Paging in GET /v1/op/jobs/dispatching-jobs/{jobId}/processing-jobs doesn't work

APIs & Connectors
1

Dear Visier developer community,

As specified in the Data and Job Handling API in order to get the status for the processing jobs (for a dispatching job), one can call the endpoint GET /v1/op/jobs/dispatching-jobs/{jobId}/processing-jobs. When we call the endpoint by setting the start query parameter to a value higher than zero, we get an empty list for the field processingJobs.

For example when we execute the following request:

GET v1/op/jobs/dispatching-jobs/<VALID-DISPATCHING-JOB-ID>/processing-jobs?limit=50&start=1

we get the following response:

{
	"parentJobId": "<VALID-DISPATCHING-JOB-ID>",
	"parentTenantCode": "<VALID-ADMINISTRATIVE-TENANT-CODE>",
	"limit": 50,
	"start": 1,
	"processingJobs": []
}

When we call the endpoint by setting the start parameter to 0 and the limit parameter to 200, we only get 100 processing jobs, although the dispatching job contains (via the extraction jobs) more than 1000 processing jobs.

Are we setting query parameters wrongly or is the API somehow not respecting the values for the start & limit parameters.

Best regards

2

Hello @b.zafirov ,
Thanks for logging this. I’ve forwarded these details to the appropriate dev lead to look into.

Thanks,
/Henrik

3

Hello @henrik.areskoug,

What’s the status of this issue? Could you give us an ETA on this, as this endpoint is a blocker for us?

Best regards

4

Hello @b.zafirov ,
We are actively looking at this and are targeting the June 5th patch.
Thanks,
/Henrik