I am using copilot studio latest version with harness and i am facing issue with file content

Use the file from System.Activity.Attachments and pass both the file name and file content explicitly to the Outlook action. The corruption happens when only the file name is passed and contentBytes is empty or mapped incorrectly.

Recommended setup:

1. In the topic, first capture the uploaded file.
   • Use a Set variable value node with:

          First(System.Activity.Attachments)
     

   • This returns the attached file as a record.
2. Extract the two fields needed for email attachment handling:
   • File name: .Name
   • File content: .Content
3. If the user might start the conversation with or without a file, combine both patterns:
   • Check First(System.Activity.Attachments) first.
   • If no file is present, route to a Question node with Identify = File.
   • In the Question properties panel, enable Include file metadata.
4. For Send an email (V2), the attachment input must be wrapped as a record with contentBytes and name keys.
   • Use this shape:

          { contentBytes: Topic.userReceipt.Content, name: Topic.userReceipt.Name }
     

   • If filling from System.Activity.Attachments directly for a tool, use:

          If(
              IsEmpty(System.Activity.Attachments), 
              [], 
              [{ contentBytes: First(System.Activity.Attachments).Content, name: First(System.Activity.Attachments).Name }])
          )
     

5. On the Tools page, file inputs must be set with Custom value and a Power Fx formula.
   • Do not use Dynamically fill with AI for file inputs.
6. If the file still appears empty, verify channel and environment support:
   • File input is supported on Microsoft Teams, custom website/demo website, Facebook, Omnichannel for Customer Service, Microsoft 365 Copilot, and the Test your agent panel.
   • File input is not supported on voice, telephony, or SharePoint channels.
   • In a customer managed key enabled environment, files can be added as input, but the agent does not process them.
7. Check file limits and behavior:
   • Maximum attachment size is 16 MiB per file.
   • Failed attachments are skipped and the message still continues.

For the scenario described, the most likely fix is:

• store First(System.Activity.Attachments) in a variable,
• map .Content to contentBytes,
• map .Name to name,
• and pass the attachment object to Send an email (V2) using Custom value.

If only the name is available in the current topic path, the file was not captured through the file input path correctly, or the attachment input was mapped in the wrong format.

References:

• Pass files to agent flows, connectors, and tools
• Attach files to a conversation
• Allow file input from users