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***