Can you share the version you're on and
Can you share the version you're on and similar details per email again please
9 Replies
v1.244.4-2-g9fffe4f6f
Basically, scheduled flows will sit in limbo with execution time running but no workers attached. It will not schedule the next one until you force kill it, thus that flow schedule is effectively dead even if you have "no overlap flows" disabled.
Once you stop/stop the schedule, it will create a new schedule (for example, I have it hourly, but it can be dead for days if I don't check regularlly).
This started happening a month ago, been running for months prior without a single occurance of this.
This one was stuck running for 134K seconds, preventing any hourly scheduled ones from running for a few days.
The moment I start/stop the schedule, a new one shows up for the next hour, but I need to manually cancel & then force cancel the limbo ones.
Can you share the flow_status of the leaf flow that is running
That's the only info I need
Where do I get that?
I canceled the last running one, so I'd have to wait for another halt if you need an active one.
Yes let's wait for the next one
Can you let me know where to get what you need so I can grab it and send it over when I have a failed one.
yes, you will have to go your in your browser's developer tool, network tab, and share the json result of all the requests that have a
/get_u in them
also if you can go in your worker logs and check if the worker processing it didn't panic and restart that would be greatI sent these over before via email, they didn't help?