Attachment with key None not found in UiPath or local storage

Business Orchestration and Automation
1

I am trying to run the Paystub validation agent provided in the academy under IXP course. I am getting this error on execution, can anyone please help and guide.

Error: Execution error: An unexpected error occurred during agent execution, please try again later or contact your Administrator.
Error Details:
Attachment with key None not found in UiPath or local storage

2

@Jinz_J

Check whether your passing the any file or not if yes check how you are passing whether it is a filepath or different and if you are using storage bucket check whether that filename is exactly matching or not.

3

Hi @Jinz_J,

This error usually occurs when the agent is not receiving the attachment correctly. “key None not found” typically means the file input is missing or not mapped properly.

A few things you can check:

  • Ensure the file is actually being passed to the agent (not null/empty)
  • Verify whether you’re using a local file path or Storage Bucket, and that the path/name matches exactly
  • Check the input schema of the agent—make sure the attachment key is correctly configured and mapped
4

Hi,

I have the same error but in a different context, the existing answers didn’t solve my issue so I wanted to share my findings.

In my case, the file mapping is correct and the storage bucket works fine. The IXP tool only works when a file is deposited directly into it manually. As soon as it is called from an agent, including brand new agents created from scratch for testing, it fails systematically with this error. Worth noting that using the native Analyze Attachment tool works perfectly — the agent correctly processes the PDF — which confirms the file itself is not the issue.

This suggests the issue is specifically tied to how the agent passes file attachments to the IXP tool, not to the file or its configuration.

Is anyone else experiencing this ?

5

I passed the PDF file as an input argument of type ‘File’ . So not sure why it failed. Apparently for another IXP process it worked fine, maybe intermittent issue. Thanks all for responding.