Schedule not followed, skips runs
Hi - I've had this issue for a while but haven't posted - my schedule doesn't run as normal, it consistently skips runs. Sometimes it works for a few days then goes back to skipping.
As pictured it should be running every 12 minutes, but the next run isn't for 5+ hours. If I turn off and back on the schedule it schedules a next run correctly soon, but then it adds another big gap again. Any ideas? Much appreciated!
As pictured it should be running every 12 minutes, but the next run isn't for 5+ hours. If I turn off and back on the schedule it schedules a next run correctly soon, but then it adds another big gap again. Any ideas? Much appreciated!
7 Replies
I have both "no overlap of flows" on as pictured, and also concurrency limit 1, not sure if these could be conflicting perhaps
Ideally my goal is for one worker to be "always running"
when no overlap of flows is set, the next run will only be scheduled after the current run is done, so if your run is longer than 12min, runs will be skipped
thanks Hugo - I may be misunderstanding how it's supposed to work.
in my original messages, my runs were averaging about an hour, but the next run was scheduled for 5+ hours out. is that expected behavior?
in my original messages, my runs were averaging about an hour, but the next run was scheduled for 5+ hours out. is that expected behavior?
concurrency limits can also affect it, you should see some logs in the flow if it was rescheduled for later
are you selfhosted or on the cloud?
i'm self hosted EE... i don't see anything in the logs, but not sure it should appear here. logically, it doesn't seem like concurrency should be an issue? that said, i disabled the concurrency setting and it is working as i'd expect now. so my immediate needs are solved, but something you might want to look into 🤷
appreciate your responses!
Do you still have the "no overlap of flow" option enabled?
Also it seems your queue is super full and jobs have to wait a lot (300s+) before being picked up