On the TriggerBotByProcessAndRobotName server action there is a GET API call named GetRobotByName to retrieve the RobtId using the RobotName input argument.
But we found this RobotId is never used in the TriggerJob API call. So we had no success in running this action.
Furthermore, the GET API call to /odata/Robots doesn't return the robots on newer UiPath Orchestrator versions. A call to /odata/Robots/UiPath.Server.Configuration.OData.GetConfiguredRobots may be needed in these cases.
I'm sending attached a version of this connector with the action TriggerBotByProcessAndRobotName we edited to get action running successfully.
Hi Alexandre,
Thank you so much for your example! To accommodate some changes in the UIpath api,and to be flexible with the different deployment scenarios and strategies, we recently had to add additional Server Actions and logic, depending on strategies invoked. It's possible there are other deployment/robot scenarios that we didn't account for in the creation of this component. I will investigate these changes and where possible update the component.