topic Re: Databricks missing scheduler for scheduled jobs in Get Started Discussions

Databricks missing scheduler for scheduled jobs

Teja3051 — Tue, 12 May 2026 08:47:25 GMT

Suppose a job is scheduled at 2 am but if scheduler misses it we need to get an alert message how can it be possible.we don't have centralised table monitoring and APIs for it

Re: Databricks missing scheduler for scheduled jobs

KrisJohannesen — Tue, 12 May 2026 08:54:54 GMT

If the job is scheduled it will run - I don't think you need to worry about that in general.

If you want to be sure, you can setup email notications on "Start" to get notified that it is actually starting up.

Additionally you can also query the jobs api to see what jobs have run and when if you want.
https://docs.databricks.com/api/workspace/jobs/listruns

Re: Databricks missing scheduler for scheduled jobs

Teja3051 — Tue, 12 May 2026 09:36:30 GMT

The problem is sometimes the scheduler is missing the scheduled time that's and we can't use on start because if the job may ran about 40 times in a day for us and another prblm is we are already using this notification for on failure we can't use it for on start ,is there a possibility to get an alert when the job didn't ran for the scheduled time

Re: Databricks missing scheduler for scheduled jobs

Ashwin_DSA — Tue, 12 May 2026 09:49:47 GMT

Hi @Teja3051,

Yes, it is possible for a scheduled run to be delayed or skipped, so I’d first recommend identifying the root cause before putting an alerting workaround in place. Common things to check are scheduler or cloud delays of a few minutes, max concurrency causing a run to be skipped because another run is still active, and timezone/daylight saving behaviour if the schedule is not using UTC.

Once that investigation is done, if the requirement is specifically to alert when the 2 AM run never starts, the usual approach is to add a separate watchdog check. For example, you can just run a small SQL query after 2 AM to verify that the expected run exists, and then trigger an alert if it does not. That works well here because native job notifications cover start, success, failure, and duration warnings, but not a dedicated "missed schedule" event.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.