cancel
Showing results for 
Search instead for 
Did you mean: 
Get Started Discussions
Start your journey with Databricks by joining discussions on getting started guides, tutorials, and introductory topics. Connect with beginners and experts alike to kickstart your Databricks experience.
cancel
Showing results for 
Search instead for 
Did you mean: 

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

jgrycz
New Contributor III

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`. 

Screenshot 2023-08-03 at 09.23.13.png

5 REPLIES 5

jgrycz
New Contributor III

Thanks for the response @Retired_mod !
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?

 

Hubert-Dudek
Esteemed Contributor III

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

jgrycz
New Contributor III

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
New Contributor III

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
New Contributor III

@Hubert-Dudek @Retired_mod 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?

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now