{
"message": "The job's associated process could not be found",
"errorCode": 1002,
"traceId": "00-8af634a7c28e15235b9edf063ae70c22-90e52267d0feb38b-00",
"resourceIds": null
}
I have traced the process from the web orchestrator
I have checked the post:
I got the machine id using /odata/Machines
and I got the robot id using odata/Sessions/UiPath.Server.Configuration.OData.GetGlobalSessions?$expand=Robot($expand=License)
because odata/robots returns empty.
Moreover, I am using a local user account with all permissions assigned
An easy approach to identify what might be being overlooked is to use your Browsers Inspector to capture the Requests and then perform the actions within the WebUI.
From here you should be able to replicate the actions and payload and then as a final step I generally cleanup any attributes/properties that are not required.
Thank you for your reply, if I added the process key alone it works fine in classic folders. However, when using modern folders , I inspect my browser I have found more attributes than what I have found in the startJob documentation and I have tried to send the request using these attributes still no luck.
I think the problem might be related to the the local user I am using. since I’m not using a robot account. So should I use robot account instead or it does not matter?