UiPath Invoke Agent - Failing

[Ritaman_Baral]

I have invoked an UiPath agent in studio web

Then agent should be provided “File” type as in_argument

I have cross validated everything and it’s fine but the agent is failing with the error mentioned in the screenshot.

[Dhruba_Jyoti_Kalita]

@Ritaman_Baral It looks like the issue is happening while passing the File input to the agent.

Can you check these once:

1. In Agent Builder, confirm the input argument type is set to File.
2. In Studio Web, make sure you are passing the actual File variable to the agent, not the file path as a String.
3. Try running the agent directly from Agent Builder with the same file. If it works there but fails from Studio Web, then the issue is most likely with the file mapping during Invoke Agent.
4. Also try once with a small PDF or TXT file to rule out any file-specific issue.

The ResponseNotRead message looks like a runtime/streaming response erro

[Jasmin_Bar]

Hi @Ritaman_Baral ,
The error is likely related to how the File input argument is being passed to the UiPath Agent rather than the agent logic itself. Verify that the file is uploaded to the correct storage location (Storage Bucket/Agent input), the argument type is exactly File, and the agent has permission to access the file. Also try testing with a small sample file and republishing the agent. The ResponseNotRead message can indicate an issue in the agent runtime or Studio Web when processing the file stream, so checking agent logs and updating to the latest version is recommended.

Thanks

[Ritaman_Baral]

I have validated and everything looks good

[Dhruba_Jyoti_Kalita]

Great @Ritaman_Baral Please mark my solution as Resolved.

Thanks

Dhruba

[imad-pro (Imad Eddine Berjamy)]

Hey @Ritaman_Baral

The ResponseNotRead message points to an issue reading a streaming response, but it doesn’t necessarily mean your File argument is incorrect.

I’d start by testing the agent independently through an evaluation, uploading the same file. Use an actual evaluation run, since file inputs aren’t supported in simulation mode.

If that works, check that the calling workflow passes the file output from the download activity into the agent’s File input, rather than just the filename or storage bucket path. The agent also needs a tool capable of processing the file, such as Analyze Files, IXP, or an RPA workflow.

If the independent test fails too, check the agent trace to see which tool or model call fails and whether there’s another error before ResponseNotRead. That should help identify where the issue starts.

Could you share your input mapping and the first failed step in the agent trace, with any sensitive information hidden?

[Ritaman_Baral]

Hey thanks for the explanation.

[imad-pro (Imad Eddine Berjamy)]

@Ritaman_Baral Glad it worked! If this solved the issue, could you please mark the reply as the solution? It might help others who run into the same problem.