"Orchestrator information is not available. Please check if UiPath Robot Service is started."

[rpamania]

The following pertains to UiPath version 2023.10.4.

I’m trying to invoke Get Queue Items activity by dynamically setting the QueueItemStates property in code in order to avoid having to insert multiple instances of the activity along with conditional statements to cover all checkbox combinations. I’m programmatically preparing the activity instance using following assignments and finally executing the activity using WorkflowInvoker.Invoke().

GetQueueItems activity = New GetQueueItems With { 
    .QueueName = "myQueueName", 
    .Top = 100
}

activity.QueueItemStates = QueueItemStates.New

IEnumerable(Of QueueItem) ienumQueueItems = WorkflowInvoker.Invoke(Of IEnumerable(Of QueueItem))(activity)

Trying to invoke the activity this way will always fail with the exception specified in the message title. Note that if I run the same activity as a classic activity block, everything works just fine…no exceptions are thrown and queue items get retrieved. So it seems there’s something about the code-based approach that works differently behind the scenes.

I’m really curious as to why preparing and running the activity with assignments doesn’t work while executing the activity block does. I’ve checked the Get Queue Items activity’s code in a decompiler and I haven’t been able to find an obvious reason. The only hint I’ve found is that the exception is caused by context.GetExtension<IWorkflowRuntime>().OrchestratorSettings.ConfigurationUrl string property not being available or having been set.

[sven.wullum1]

Hi!

Take a look at this documentation and see if that helps:
Activities - GetQueueItems (uipath.com)

[rpamania]

This seems great, but none of the UiPath.System.Activities.Api.dll assembly versions that I’ve checked contain the namespace UiPath.Activities.System.API or public API methods.

[rpamania]

Well, turns out the API works fine. UiPath documentation just has outdated info about the namespace. You’ll also have to access the API method via coded workflows, as they are directly unavailable in classic .xaml workflows.