Period Tasks Don't Adjust for Daylight Savings

[harelw]

I have a periodic task set with a crontab of 0 14 4 * * (Every Thursday at 2 PM) and TIMEZONE for Django set to America/Los_Angeles. Upon the recent change in time, it now triggers at 3 PM Los Angeles time, as if Daylight Savings hadn't started.

I do not have a different timezone set for Celery.

[harelw]

This seems to have corrected itself over time, but it was off for one triggering.

[amitripshtos]

Had the same issue - on the daylight saving day all my tasks got scheduled badly.

[steveweldon]

@auvipy @harelw any idea if this is fixed in newer versions? Just had the same issue where tasks executed an hour later on daylight savings day, but triggered correctly the day after.

[ShanoZen]

I also experienced this issue. All crontab scheduled commands during daylight saving day suffered. Running in the old time, instead of the new time.

[sudarshaana]

Any update whether it is fixed or still exists?

[konurbaev-e]

Team, any update on this issue?

We encountered the same problem yesterday due to daylight saving time in New York.

Our jobs are scheduled to run daily at 16:04 in the America/New_York timezone (CrontabSchedule).

However, on March 9, the job ran at 17:04 instead.

The celery version is 5.3.4 (emerald-rush).

[robin-repowered]

Had this exact issue yesterday with starting DST in Europe/Amsterdam timezone.

The schedule self-corrected for the next day.

[auvipy]

is this PR related #605 ?