Get Orchestrator asset: error 404 Not Found

Hello, I’m having trouble to link Studio with the assets and queues created in Orchestrator.
When running the initializing of the ReFramework, the following error message occurs:
2026-05-1113-45-21


I have entered the assets in the config file
2026-05-1113-42-37
and created it in Orchestrator
. Can someone tell me what is wrong? Thanks in advance, Riana

Hi @Riana

Can you check the properties of the “Get Orchestrator asset” activity and make sure you have specified the correct folder “CFD\FA” where the asset sits?

Secondly, make sure your Studio project status (green bar at the bottom) is connected to that same folder when debugging

@Riana

Expand the folder path value and see if it’s not in “”. Sometimes the studio just wraps the value in “” and consider everything we pass as string instead of expression.

@Riana

Before directly giving the values in the activity,

check whether values are coming properly or not. And ensure your studio connected with same tenant.

use log messages or immediate panel to check the values are coming correctly or not.

This is not a direct answer, however. Its been my strong opinion for several years that managing assets from an Excel config like this should not longer be best practice.

I’d suggest simply removing those values entirely from your config, and adopting a more modern approach, which is to use the get asset activity right before you need to use it, and selecting the values you require in the dropdown. It can validate them at design time now and if you do it this way the package requirements in the Orchestrator can tell you if any assets are missing before you even run the automation.

Hi @Riana , Make sure you have the correct folder name

In your case, your folder name - CFD/FA/13729

and also does your robot connected to which folder? if it is connected to CFD/FA/13729 then you don’t need to pass the folder name at all

@Riana

It would have been due to recent outage of the platform. If the configuration is good then the outage was the issue. You can retry now.

Click the refresh button on the bottom right and try again.