The API documentation does not explicitly specify the order in which jobs are returned. Anecdotal evidence suggests that the default ordering is descending by creation time. Additionally, such ordering seems to remain consistent across API calls unless altered by pagination or filtering.

 

To verify this, I also reviewed internal (non-public facing) documentation, which states:
"The response from the Databricks Jobs API /api/2.2/jobs/list does not explicitly define the ordering of jobs in the returned list within the provided documentation. There is no confirmed indication in the referenced materials whether jobs are ordered consistently or by specific fields such as creation time. Hence, it is likely that the ordering could be either random or implementation-dependent."

I hope this information proves helpful.

 

Best regards,
Louis