Orchestrator Swagger API Problem

I am trying to start a job on our on-premise Azure based Orchestrator via the Swagger API, I can authenticate fine, I can obtain a list of processes fine, however when I try to create a job via the StartJobs request below I am returned a response 500 (I can manually create the job with the same user account in the Orchestrator UI).

Swagger UI

“startInfo”: {
“ReleaseKey”: “BlankProcess:1.0.1”,
“Strategy”: “All”,
“RobotIds”: ,
“NoOfRobots”: 0

Response Code 500

Response body is

Swagger UI

“message”: “An error has occurred.”,
“errorCode”: 0,
“resourceIds”: null

Response Headers is 

  "cache-control": "no-cache",
  "pragma": "no-cache",
  "content-length": "69",
  "content-type": "application/json; charset=utf-8",
  "expires": "-1",
  "request-context": "appId=cid-v1:0db55206-67ed-4b54-8de9-88e37762512a",
  "access-control-expose-headers": "Request-Context",
  "x-content-type-options": "nosniff",
  "x-frame-options": "DENY",
  "strict-transport-security": "max-age=31536000; includeSubDomains",
  "date": "Fri, 10 Jan 2020 13:16:12 GMT",
  "": ""

Sorted it, I made the mistake of supplying the Key of the process I wanted to start not the Key of the process’s release!!!.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.