cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Scheduled job did not trigger the job run

brickster_2018
Esteemed Contributor
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

brickster_2018
Esteemed Contributor
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

brickster_2018
Esteemed Contributor
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

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!