We have upgraded our OnPremise to the latest Orchestrator version. Now, we are facing an issue with our API script “Job Start.” Before the update, this process was working fine, and we hadn’t made any changes.
Error message: “{“message”:“The robots already have pending jobs for this Process”,“errorCode”:1670,“traceId”:“00-bf8096c67bbd29f69452084c8068b686-ab302d3f4ad9ecfe-00”,“resourceIds”:null}”
We have set up the folder structure in a way that divides our processes into folders and subfolders. This process is located in the folder xyz/Unattended.
In the HTTP Request header, we have specified the path as well: X-UiPath-FolderPath: “xyz/Unattended”
When we use this path, we get the aforementioned error message with pending jobs, but no job appears in Orchestrator.
However, if I change the path to: X-UiPath-FolderPath: “Default,” the API job starts, but it starts in the Default folder. Of course, it doesn’t run there because no robots are assigned to that folder.
Am I missing a setting that needs to be configured so that the process can be started in the correct folder, or is it not possible to start processes in modern folders via the API, and I should start the API processes in the Default folder?
Just for your information, as mentioned, the process is working and configured correctly. There seems to be an issue somewhere with the execution of the process.