Failed to load asset: "DocumentUnderstandingApiKey" in Orchestrator and Document Understading

Hi All,

I am planning to run document understanding process via orchestrator. But I am getting below error;

“Failed to load asset: DocumentUnderstandingApiKey”

I was able to successfully trigger the flow using UiPath Studio after adding all the Asset values, but when I try to run it un attended it’s not working.

Appreciate your kind support to resolve this issue.
I checked all the Asset name and values too, not they are same :frowning:

Thanks in advance.

@Kavindu_Dilshan1

Check if the asset is available in the correct folder too and robot have access to that folder.

Thanks @ashokkarale for the reply. It’s in the correct folder. Could u please share more info on how to check the access for the robot?

Thanks

Can you please share screenshot of where the aseet is kept in orchestratrtor and also UiPath studio code screenshot like how are you using Get Asset

Could be that asset is present in folder.

But you are passing the incorrect folder path for this asset..
Reverify again and give it a try..

Ho @chandresh_agarwal ,

Please find the below screenshots;

I am using UiPath default document understanding template;

Hi @MohammedShabbir ,

I am using the same folder name as in Orchestrator;

Try to check you value for orchestrator folderpath and asset name by using message box or either in watch panel by applying breakpoint on get asset.

Hi @Kavindu_Dilshan1

This is usually a folder or robot access issue.
Make sure the DocumentUnderstandingApiKey asset exists in the same Orchestrator folder where the unattended job runs, the asset type is Text, and the unattended robot has access to that folder.
If it works in Studio but not unattended, it’s almost always an Orchestrator folder/permission mismatch.

Hi @Monali_Vekariya Thanks a lot for your reply.
I checked access too, but appreciate if u could share exact locations to check?
I am not too sure how to check the accesses for this?

Thanks

check your UiPath assistant application, please check if the status is connected,licensed it means your studio is connected to orchestrator.

another one is to check for assetname in your config file. should be on “Asset” Sheet.

check your initallsettings argument value if the sheet on where the apikey is stored is already there.
image

  1. Go to Orchestrator → Folders
    Open the folder where the unattended job is running.

  2. Inside that folder, go to Assets
    Confirm DocumentUnderstandingApiKey exists there and the name matches exactly.

  3. Go to Tenant → Machines / Robots
    Open the unattended robot and make sure it is assigned to that same folder.

  4. In the folder → Users / Robots
    Check that the robot has access (not just the user).

If Studio works and unattended doesn’t, it usually means the asset is in a different folder or the robot isn’t mapped to it.