Hi,

since April 1st (2026) we are having problems calling the databricks /api/2.2/jobs/runs/list and the /api/2.0/sql/history/queries endpoint. Calls to these endpoints sometimes seem to take longer than 60 seconds now using the databricks python sdk which leads to our script being killed.

What we do explicitly is implementing monitoring with Icinga2 for our job runs and queries, looking for runtime issues. This means that for the jobs we have our Icinga query the databricks jobs api for each of our jobs (which are 48 in one workspace at the moment) every 3 minutes. As far as I understand the documentation, the rate limit for the /jobs/runs/list is 30 calls per second per workspace so my understanding is that we should not run into rate limits.

Extending the Icinga timeout also shows, that the databricks api does not return any error, its just that establishing a connection apparently takes a really long time sometimes. What I find curious about this is that we only started having problems after the 1st of April without doing any changes in our setup. So I was wondering if there maybe were some changes done to the api?

Or could there be another explanation for this behaviour? We are running our workspaces on gcp in the zone "europe-west1".