cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Scheduled job did not trigger the job run

User16869510359
Esteemed Contributor

I have a job that is scheduled to run every one hour. But rarely I see the job runs are skipped

1 ACCEPTED SOLUTION

Accepted Solutions

User16869510359
Esteemed Contributor

If you choose a timezone with Daylight savings this issue can happen. We recommend choosing UTC timezone to avoid this issue. If you select a zone that observes daylight saving time, an hourly job will be skipped or may appear to not fire for an hour or two when daylight saving time begins or ends. Hence, to run at every hour (absolute time), choose a UTC time.

Read more here:

https://docs.databricks.com/jobs.html#schedule-a-job

View solution in original post

1 REPLY 1

User16869510359
Esteemed Contributor

If you choose a timezone with Daylight savings this issue can happen. We recommend choosing UTC timezone to avoid this issue. If you select a zone that observes daylight saving time, an hourly job will be skipped or may appear to not fire for an hour or two when daylight saving time begins or ends. Hence, to run at every hour (absolute time), choose a UTC time.

Read more here:

https://docs.databricks.com/jobs.html#schedule-a-job

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.