https://prefect.io
Join Slack
Hello, Is there a reason that some flows end up stuck in the running state? I’m assuming this has to...
# ask-community
a
Hello, Is there a reason that some flows end up stuck in the running state? I’m assuming this has to do with some error handling somewhere but is this a known issue? Most of our runs are launched from laptops talking to a remote prefect server. Is there something that we should be doing to prevent this from happening? This results in a lot of confusion for our users so any ideas/suggestions would be helpful here.
b
Hey Abhinav, thanks for posting this. I'd recommend checking a few things to see what could be the reason for the flow runs getting stuck in a state of `Running`: • Agent logs • Flow run logs • Workqueue health
If possible, I'd also recommend enabling DEBUG level logs if you haven't already to see if more information can be uncovered.
Here's some github issues to check out preliminarily as well: 1. Flow still in "Running" state when agent is down: This issue discusses a flow that remains in the running state even after the agent's process is stopped. 2. Flows with "Crashed" subflows that exceed flow timeout stuck in "Running" state: This issue describes a situation where a parent flow remains in the running state even after its subflow has crashed and the flow timeout has been exceeded.
a
@Bianca Hoch So all the issues we’ve seen are when we launch flows from our local laptops instead of directly from prefect agents remotely.
7 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by