You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timezone of my server is set to +0900, but it seems that scheduled tasks are operating based on UTC.
$ timedatectl status | grep "Time zone"
Time zone: Asia/Seoul (KST, +0900)
For example, a cron expression like 0 9 * * *, which I intended to run at 9 AM local time, is actually being executed at 6 PM local time. Is this behavior intentional? Are there any plans to support using the server's local timezone for scheduling?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The timezone of my server is set to +0900, but it seems that scheduled tasks are operating based on UTC.
For example, a cron expression like
0 9 * * *
, which I intended to run at 9 AM local time, is actually being executed at 6 PM local time. Is this behavior intentional? Are there any plans to support using the server's local timezone for scheduling?Beta Was this translation helpful? Give feedback.
All reactions