cron: a schedule should have a next event: InvalidTime
Hi,
I'm not sure this is the right place to report this, but hopefully it reaches the right people.
We noticed some schedules failing during the transition to "winter" time, the night between 25 and 26 October. Since Windmill has been stable both before and after the switch from daylight savings I believe it might be related to rewinding the clock.
- Windmill version: CE v1.476.0-2-g09f4ee22b
- Worker logs are attached
- The error is consistent in the sense that all our schedules for the range of time close to 00:00 the 26:th failed with the same error. All our workers were affected
- I'm not sure the flow is relevant since this error affects all our flows. But if I'm wrong just tell me and I'll provide one
- The infra is based on docker compose, three workers. The setup is simple, all on the same machine with 100GB storage, 32GB RAM, 8 vCPUs.
The actual error seems to be:
Any ideas on how we can avoid this?
I'm not sure this is the right place to report this, but hopefully it reaches the right people.
We noticed some schedules failing during the transition to "winter" time, the night between 25 and 26 October. Since Windmill has been stable both before and after the switch from daylight savings I believe it might be related to rewinding the clock.
- Windmill version: CE v1.476.0-2-g09f4ee22b
- Worker logs are attached
- The error is consistent in the sense that all our schedules for the range of time close to 00:00 the 26:th failed with the same error. All our workers were affected
- I'm not sure the flow is relevant since this error affects all our flows. But if I'm wrong just tell me and I'll provide one
- The infra is based on docker compose, three workers. The setup is simple, all on the same machine with 100GB storage, 32GB RAM, 8 vCPUs.
The actual error seems to be:
Any ideas on how we can avoid this?
wm-worker.log8.9KB
