UiPath Academy REFramework Exercise

Help Orchestrator
,
1

I’m taking the UiPath Academy course ‘Building a REFramework Project with Orchestrator Queues’.
When I run it in Studio in Debug Mode, or Run Mode, everything works fine.
Then I uploaded the project to Orchestrator and launched it as a Job, and here it throws an exception, and says that a Key is not in the dictionary generated from the Config file, but it does exist and in debug mode I have been able to verify that both the Key and the Value exist.
Can someone explain to me why it fails from Orchestrator but works correctly from Studio?
I leave some screenshots:

The image shows a software interface with two instances of "Academy-REF-UiDemo" marked as "Faulted" with medium priority, both running under user "CUEVAS" on "DESKTOP-A1BGC..." with statuses indicating manual handling and recent runtime durations. (Captioned by AI)

A log entry showing various transactions and processes with timestamps, primarily marked as "Info" with one "Error" indicating a missing dictionary key. (Captioned by AI)
A log entry showing various transactions and processes with timestamps, primarily marked as "Info" with one "Error" indicating a missing dictionary key. (Captioned by AI)1665×222 43.3 KB

The image shows a series of logged actions and statuses related to the execution of the UiDemo application, including starting and ending a transaction, with various details such as screen resolution, process initiation, and transaction success noted. (Captioned by AI)
The image shows a series of logged actions and statuses related to the execution of the UiDemo application, including starting and ending a transaction, with various details such as screen resolution, process initiation, and transaction success noted. (Captioned by AI)707×317 12.8 KB

2

@Antonio_Perez,

Can you try deleting all the package version of the project you are working on from Orchestrator. Once deleted everything publish it again and create a process.

Now delete the package from your bot running machine’s .nuget package path like this: C:\Users\yourusername\.nuget\packages

Once this is done, now trigger the bot from Orchestrator or Assistant as you were trying.