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
There is an issue with Schedules not aligning properly with different time zones. When a pipeline is scheduled with a certain cron expression, it does not run at the expected local time due to time zone differences. For instance, a pipeline scheduled with the cron expression 0 9 * * * actually ran at 11 AM instead of the expected 9 AM.
Reproduction steps
This issue can be reproduced by setting up a pipeline with a specific cron expression and observing the time it actually runs, which differs due to the time zone. Here's an example:
The scheduled pipelines should run according to the local time zone of the user or the server where ZenML is running, or there should be clear documentation and warning messages indicating the time zone in which the schedules are interpreted.
Potential Solutions
Implement a technical solution that adjusts the scheduling time based on the user's or server's local time zone.
Provide a warning or error message in the ZenML interface to indicate the time zone used for scheduling.
Add documentation specifying the behavior of the scheduler with regards to time zones, especially if it runs on UTC time by default.
Additional context
This issue is crucial for users who rely on precise scheduling for their pipelines, particularly in a global context where users may be in different time zones.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@ashutosh887 you're welcome to do so. Might be worth picking one of the two you mentioned and starting with that one first, but go for it! Let us know if you have any questions or to propose how you might tackle the issue (once you've dived into it a bit).
Open Source Contributors Welcomed!
Please comment below if you would like to work on this issue!
Contact Details [Optional]
support@zenml.io
What happened?
There is an issue with Schedules not aligning properly with different time zones. When a pipeline is scheduled with a certain cron expression, it does not run at the expected local time due to time zone differences. For instance, a pipeline scheduled with the cron expression 0 9 * * * actually ran at 11 AM instead of the expected 9 AM.
Reproduction steps
This issue can be reproduced by setting up a pipeline with a specific cron expression and observing the time it actually runs, which differs due to the time zone. Here's an example:
Expected behavior
The scheduled pipelines should run according to the local time zone of the user or the server where ZenML is running, or there should be clear documentation and warning messages indicating the time zone in which the schedules are interpreted.
Potential Solutions
Implement a technical solution that adjusts the scheduling time based on the user's or server's local time zone.
Provide a warning or error message in the ZenML interface to indicate the time zone used for scheduling.
Add documentation specifying the behavior of the scheduler with regards to time zones, especially if it runs on UTC time by default.
Additional context
This issue is crucial for users who rely on precise scheduling for their pipelines, particularly in a global context where users may be in different time zones.
Code of Conduct
The text was updated successfully, but these errors were encountered: