We run an automation through a Power App/Power Automate flow that calls to the UiPath Orchestrator - this automation requires us to push input arguments in order to run the bot. Our Power App uses a flow that calls the Orchestrator GetJobs API to get the status of the jobs, which relies on it also parsing the response for the input arguments that were provided to it.
Between March 11 and March 13, 2024, something seems to have changed with the API as it’s no longer passing our input paramters back through that API, simply showing ‘null.’
Any help in understanding what changed so we can fix it and properly retrieve our input arguments from the Orchestrator Get Job API?
Can you show what call you are making and what you are getting?
Is the status code 200 or something else
As it is community version generally there would be frequent updates and there might be some change as wel but cannot confirm that it is because of that only till you give more details
Community Edition provides free access to users who in turn provides free testing to UiPath.
Unfortunately this does mean things will break frequently and may not be fixed for a while.
Your best bet would be to find a workaround until this is fixed (hopefully).
The alternative would be to purchase a license as you will then have the ability to:
Withhold updates to preserve stability
Roll back to older package version when an update breaks the bot
Lodge a ticket with UiPath support to assist you
Can the flow check for something else to get status of the jobs?
Can the UiPath process be modified to leave some info at various stages in the process that the flow can read instead?
Thank you for sending this - it did lead me to the right documentation that states specifically that these fields were removed from the API in an effort to reduce size of the API calls, and that any call to them would result in a ‘null’ response.
Looks like I have to figure out a workaround! Thanks
)? It seems like it should be one of the workarounds they’re presenting, but I’m getting an error response when trying to use via Postman or Power Automate HTTP activities:
Swagger has the call listed as well, but it’s indicating the Key is supposed to be an integer. Which is different than my every single interaction with the Job Key (only ever seen it as an alpha-numeric value) - also added as a screenshot
