Starting queue items

[grzegorz.surdziel (innerstacktrace)]

The swagger documentation states that running /odata/Queues/UiPathODataSvc.StartTransaction
should be able to pick up a ‘New’ queue item and move it to ‘In Progress’.
This however seems to not work as a correct request body (with SpecificContent:null) clones the queue item anyway.

Either the documentation is incorrect or the functionality isn’t supported, most likely the former.

To support that claim I’d like to point out that RobotId parameter isn’t listed, yet accepted and correctly used, while RobotIdentifier parameter seems unusable due to no matching data being returned for robot accounts.
RobotId expects an integer arg that is available for ‘Users’ entries of type ‘unattended’ or similar. Robot identifier expects something in a UUID form.

[Anil_G (Anil Gorthi)]

@grzegorz.surdziel

ideally the endpoint works only from robot..

Orchestrator - Transactions requests

hope this clarifies..and yes this has been reported you can vote up on it

Start Transaction API call Not retrieving items

Hi Team, Used start Transaction api call with a valid robot identifier as well and the status returned is 204 but no item is picked. Please find the payload used [The image shows an example of a cURL command to start a new transaction in UiPath's cloud Orchestrator, including the request URL, headers, and response code. (Captioned by AI)] As per doc if specific content is null it would pick the available new item [The image displays a snippet of code documentation, explaining the behavior …

cheers

[grzegorz.surdziel (innerstacktrace)]

Will do.
That bit about StartTransaction being ~robot-only was known and assumed.
Therefore the feedback I guess mostly pertains to the swagger docs likely being out of date.