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:ย 

Databricks missing scheduler for scheduled jobs

Teja3051
Visitor

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 

3 REPLIES 3

KrisJohannesen
Contributor

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.

KrisJohannesen_0-1778575964175.png

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

Teja3051
Visitor

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 

Ashwin_DSA
Databricks Employee
Databricks Employee

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.

Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***