Response for list job runs API request doesn't have next/prev_page_token field

[jgrycz]

HI,

When I do GET request to obtain list of job runs using `/api/2.1/jobs/runs/list` there is no `prev_page_token`, `next_page_token` fields in the response despite of having `has_more: True`. 

[Kaniz_Fatma]

Hi @jgrycz, Based on the provided information, the /api/2.1/jobs/runs/list API endpoint returns a list of runs in descending order by start time. It includes a has_more field in the response indicating whether additional runs matching the provided filter are available for listing. However, there is no mention of prev_page_token or next_page_token areas in the response. Therefore, it seems that these fields are not included in the response of this API endpoint.

 Sources: https://docs.databricks.com/workflows/jobs/jobs-2.0-api.html#runs-list

[jgrycz]

Thanks for the response @Kaniz_Fatma !
Oh ok, but I did read this doc: https://docs.databricks.com/api/workspace/jobs/listruns could you confirm that it's correct one?

So are we able to get the rest of the runs?

[Kaniz_Fatma]

Hi @jgrycz, yes! It is the correct one.

[Hubert-Dudek]

There is API 2.1 available for jobs and here is better documentation https://docs.databricks.com/api/workspace/jobs/list

[jgrycz]

Yeah @Hubert-Dudek, I used that documentation to build my query and still I'm not sure why I don't have `next_page_token` field in the response.

[jgrycz]

So according to the doc: https://docs.databricks.com/api/workspace/jobs/listruns if has_more=true there should be prev/next_page_token fields as well. Can we investigate why both fields are not in the response msg?

[jgrycz]

@Hubert-Dudek @Kaniz_Fatma could you confirm that behavior is an issue? if yes, can I report it anywhere?

Otherwise can I report it as a feature request (to get all runs)? If yes, do you have any service to report it?