(sadly, I broke some eggs with the
(sadly, I broke some eggs with the change above, if you upgraded in the last 2 days and were using the "No flow overlap" feature of schedules for flows, then your schedules silently turned off). Update to latest release and re-enable those schedules to fix.
7 Replies
Would that also explain why my flow started failing with this message:
Canceled: Job canceled: Flow cancelled as it was hanging in between 2 steps by monitor
no that would be a separate issue
on what version are you ? Can you update to latest release and see if you can reproduce
1.277.1, I updated yesterday
yeah, update to 1.278.0
not 1.278.5?
I was hit by the no-overlap bug first which had caused this flow to stop. Then when I try to restart it this happens.
sure. 1.278.5
ok
So IDK if it matters, but the script which is aborted uses Python threads because it's running some very slow external tool