Start process via API

orchestrator

#1

Hello,

I run into an issue while trying to start a Job via Orchestrator API and calling StartJobs endPoint

My request body looks like that :

{"startInfo":
    {"ReleaseKey":"81634e33-9ed0-45a0-xxxxxxxx"
    ,"Strategy":"Specific"
    ,"RobotIds":[3]
    ,"Source":"Manual"
    ,"NoOfRobots":0
    }    
}

and the response is that :

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

When I set “Source” to something else like this :

{“startInfo”:
{“ReleaseKey”:“81634e33-9ed0-45a0-beb2-xxxxxx”
,“Strategy”:“Specific”
,“RobotIds”:[3]
,“Source”:“FromApi”
,“NoOfRobots”:0
}
}

the error change and become this :

{
“message”: “startJobParameters is null!”,
“errorCode”: 0,
“resourceIds”: null
}

I saw someone had the same error than my second here :

I’m in version 2018.2.3 so maybe it’s that but does it explain firt error?

Any help will be appreciate.


#2

Hi,

Maybe the examples bellow may help you?

Cheers


#3

I’m doing a call looking exactly as the one in “StartJobAPI.xaml” but I’m getting this answer :

{
   "message": "An error has occurred.",
   "errorCode": 0,
   "resourceIds": null
}

with HTTP 500 return code.

My call :

{"startInfo":
  {"ReleaseKey":"81634e33-9ed0-45a0-beb2-xxxxxxxx"
    ,"Strategy":"Specific"
    ,"RobotIds":[3,5]
    ,"NoOfRobots":0
   }	
}

#4

Could you try the following StartInfo, if you are working with the Community Orchestrator (or latest versions)?

{"startInfo":{"ReleaseKey":"c5105fa1-0bcd-4713-afd7-*******","RobotIds":[1,2],"JobsCount":0,"Strategy":"Specific","InputArguments":"{}"}}

Also, make sure that you Robots are part of the same environement as the source of the release key.

It could be helpful to know which Orchestrator version you are using

Cheers


#5

Hi Florent, thank for your help !

As I was saying, I’m using Orchestrator 2018.2.3, a paid version.

I just tried your message structure with no success here’s the answer :

{
    "message": "startJobParameters is null!",
    "errorCode": 0,
    "resourceIds": null
}

robot and process (the one associated with the release) have the same environment.


#6

We updated our orchestrator to 2018.2.6 and now the API call is OK

And i think i wasn’t giving the rights robotsIds (i was giving machine Ids) so check that again if you have the same issue.


closed #7

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