JobKey not found in Get Jobs API when executed from studio (Cloud)

[erno.palotai]

Hi all,

we retrieve the jobkey with Get Current Job Info activity. This is used by us for some reason, and works well, but we can not find the appropriate data in Get Jobs API when the process runs from studio. Is there any difference?

Thanks,
Ernő

[Jon_Smith]

The API is confusing and documented inconsistently, they often refer to the job key when they mean the job ID, with the key being a GUID and the ID being an integer.

Perhaps you need the ID from the API and elsewhere its referred to as the key?

[erno.palotai]

Hi, thanks for your feedback. No , “Get Current Job Info” activity returns a GUID (JobKey) and when we passing it to GetJobs API, it works (returns job data) if the job runs from Orchestrator (manual/trigger).
However GetJobs API return no result when job runs from studio.
Strange, but using the GUID with GetLogs api works well in all cases (also when runs from studio)

[Jon_Smith]

Yup, so the API requires the Job ID, which is an integer and not a GUID Key.
The Swagger and API documentation states you need a key, but the key it refers to is the ID, hence the confusion.

I raised it here

Swagger Documentation Inconsistencies

So I want to point out and suggest some tweaks to the Swagger documentation to make it more sensical aswell as address what I think is an inconsistency. Lets looks at a simple API call to get a Queue Item [image] It wants a Key, which should be a long, and requires an OrganisationID (this and many other requests return an error if you do not provide an organisation ID). Lets now look at a QueueItemDto where you would get information such as the ‘Key’ and ‘OrganisationID’ Here is the Key, b…

The get current job info indeed only gets the key and as far as I have seen there is no way to grab the ID from the Orchestrator without doing an additional API request.

What I do is get the key, then do an API call on the Get Jobs API and apply a filter so I only get the job with the GUID I specify and only return the ID, I use the output of this to then be able to do what I want with the job ID.

If you run a job directly in Studio it won’t have an ID as it doesnt generate a job in the Orchestrator, so there is no job to get from the API.

[erno.palotai]

@Jon_Smith

If you run a job directly in Studio it won’t have an ID as it doesnt generate a job in the Orchestrator, so there is no job to get from the API.

Thank you! This was my theory as well, that Studio jobs aren’t real jobs, but it is confusing that they got a JobKey (by Get Current Job Info) and that can be used to query logs…