Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks are not started according to local/given timezone #23257

Open
rleins opened this issue Apr 7, 2022 · 1 comment
Open

Tasks are not started according to local/given timezone #23257

rleins opened this issue Apr 7, 2022 · 1 comment

Comments

@rleins
Copy link

rleins commented Apr 7, 2022

Steps to reproduce:

  1. Schedule a task for every day
  2. Define timezone options inside the task:
    option location = timezone.location(name: "Europe/Berlin")

Expected behavior:
I expect the task started at midnight of the given timezone (in my case local timezone).

Actual behavior:
The task start at midnight UTC, which is currently (CEST) two hours off.
Every range or other timezone-related query data are correct, so it's only the starting time.

Environment info:
Docker image with correctly set timezone

@rleins
Copy link
Author

rleins commented Apr 27, 2022

I have further investigated this point.

If I set the timemask via cron, then only the first start of the task starts in Zulu time. Any next start is correct in local time.
It seems the parsing of the location-option is one step too late...

But every server restart or task re-save makes a new wrong start-time...

Furthermore it would be very nice if one could set a global location-option. So that any timezone-related operation (like tasks or functions) works with the correct timezone... No one lives in the zulu timezone 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant