Orchestrator Swagger API - Start Job

Help Orchestrator
1

Hi Guys,

I’m trying to run a Start Job via Swagger API, and am passing this as the body,

{
“startInfo”: {
“releaseKey”: “00000000”,
“strategy”: “All”,
“robotIds”: [
00000
],
“noOfRobots”: 0,
“jobsCount”: 0,
“source”: “Manual”,
“jobPriority”: “Normal”,
“runtimeType”: “NonProduction”,
“inputArguments”: “string”
}
}

But i’m always getting, “startJobParameters must not be null”, all the time. I’ve tried many variation, e.g. removing the noOfRobots, but still the same issue. Any idea?

p.s I’m using the Cloud Orchestrator
https://cloud.uipath.com/AAA/BBB/orchestrator_/swagger/index.html#/Jobs/Jobs_StartJobs

2

Please try this:

3

Still getting the “startJobParameters must not be null”.

4

Hi @kwoxer
Please check the video for reference

Regards

Nived N

Happy Automation

1 Like
5

I know, but always getting that error. Having all the header and body set. See image:

image
image691×660 19.6 KB

6

If your job doesn’t require inputs arguments

You can try with this orchestrator api call Start job

image

Mark it as solution if this resolved ur query.

Regards

Nived N

Happy Automation

1 Like
7

Well I just typed any number into X-UIPATH-OrganizationUnitId. Maybe thats my issue? But I cannot find where to get the number. You can tell me?

8

Hi @kwoxer

X-UIPATH-OrganizationUnitId is the folderid, u had to get the folder from another api call
** GET Folders - Get all**

From there u will get Id in respose, that id u need to use in the

X-UIPATH-OrganizationUnitId

Regards

Nived N

Happy Automation

1 Like
9

Perfect. Now I understand what a folder is. Great.

Ok now I get

{
    "message": "The job's associated process could not be found",
    "errorCode": 1002,
    "resourceIds": null
}

I come nearer to a solution, thanks. I recheck now the key and environment.

10

Hi @kwoxer i think there is some error in the key or something in the body argument you had provided

Kindly check that

Regards

Nived N

Happy Automation

1 Like
11

Wow interesting. Ok so I was using a Test process.

That process I released a while ago and deleted it from the process list. But internally it is still found under the “odata/Releases”. So I took a key of a “not anymore existing” process.

Just created a fresh release of that process and took that new key and it works properly now.

Thanks for your fast help. Was really helpful.

12

{

"StartInfo":{

    "ReleaseKey": "945e01ac-8806-453d-b8e1-20415309a936",

    "Strategy": "Specific",

    "RobotIds":[171711],

    "NoOfRobots":0

}

}use this