- 2037 Views
- 1 replies
- 0 kudos
Resolved! Scheduled job did not trigger the job run
I have a job that is scheduled to run every one hour. But rarely I see the job runs are skipped
- 2037 Views
- 1 replies
- 0 kudos
Latest Reply
- 0 kudos
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...
- 0 kudos
- 5266 Views
- 1 replies
- 0 kudos
- 5266 Views
- 1 replies
- 0 kudos
Latest Reply
- 0 kudos
Yes you can. Databricks maintains a history of your job runs for up to 60 days. If you need to preserve job runs, Databricks recommends that you export results before they expire. For more information, see https://docs.databricks.com/jobs.html#export...
- 0 kudos