Can't run process from Orchestrator

[loginerror (Maciej Kuźmicz)]

Hi @Kristian_R

Not being able to execute the workflow via Orchestrator that runs locally is often a sign of activity packages not being correctly downloaded from Orchestrator.

Could you see this thread to see if it helps? It is different error, but might have the same cause and solution:

Cannot create unknown type - V2018.2.3 Onwards - Troubleshooting steps

Description System.Xaml.XamlObjectWriterException: Cannot create unknown type Troubleshooting steps Explanation With Solution Approach When the process is executed from the robot, It searches for the activity version in the following location: Robot Location - C:\Users{user profile} \ .nuget\packages Orchestrator feed - ~/NuGetPackages/Activities MyGet feed - https://www.myget.org/F/workflow/ Reason of issue: The issue is because packages are not downloaded in the Robot machine and …