# Sidekiq daylight saving time issues?

**URL:** <https://meta.discourse.org/t/sidekiq-daylight-saving-time-issues/35155>\
**Category:** Bug\
**Created:** [1 Novembre 2015, 5:39pm UTC](https://meta.discourse.org/t/sidekiq-daylight-saving-time-issues/35155 "2015-11-01T17:39:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [1 Novembre 2015, 6:04pm UTC](https://meta.discourse.org/t/sidekiq-daylight-saving-time-issues/35155/2 "2015-11-01T18:04:24Z")

</div>

Interesting problem.

If daylight savings was a “standard” it would be easy enough to not run back-ups during the affected time.

But it is anything but standardized

> **[Daylight saving time | Procedure](https://en.wikipedia.org/wiki/Daylight_saving_time#Procedure)**
>
> The relevant authorities typically schedule clock changes to occur at (or soon after) midnight and on a weekend, in order to lessen disruption to weekday schedules. A one-hour change is usual, but twenty-minute and two-hour changes have been used in the past. Notable exceptions today include Lord Howe Island with a thirty-minute change, and Troll (research station) that shifts two hours directly between GMT and CEST since 2016.
> In all countries that observe daylight saving time seasonally For a m...

Maybe some way of rate limiting back-ups based on when the last successful one was run?

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-daylight-saving-time-issues/35155)._