While using Postman, on starting a specific job sending a POST request to odata/Jobs/UiPath.Server.Configuration.OData.StartJobs and the following error: "message": "The job's associated process could not be found", "errorCode": 1002"
Issue Description:
Trying to start a specific job via Postman by sending a POST request to odata/Jobs/UiPath.Server.Configuration.OData.StartJobs. The following error message is encountered: "message": "The job's associated process could not be found", "errorCode": 1002
Resolution:
When sending a request from Postman, send a new GET Release key call request adding OrgUnitId as Header. Otherwise, the output will not be associated with a specific folder and for value 1, which typically is the default folder, there will not be any process keys.
It is important to mention that the headers play an important role in determining the scope of the request to a specific folder (represented by an OrgUnitId in Orchestrator). Using the correct ReleaseKey in combination with proper "startInfo" parameters (JobsCount, JobPriority, etc.) is necessary to successfully start a job.