Tom Han
09/11/2025, 8:04 PMMarvin
09/11/2025, 8:04 PMMarvin
09/11/2025, 8:10 PMprefect flow-run ls --state Running
- Cancel one by id (moves to Cancelling/Cancelled)
prefect flow-run cancel <flow_run_id>
- Delete one by id (removes from history)
prefect flow-run delete <flow_run_id>
A couple of notes
- “Cancelled” requires an explicit cancel action (you or an automation). A hard container kill won’t auto-cancel.
- If you add a flow-level timeout, it will cancel long-running flows while the engine is alive. It won’t help if the infra is killed, but it can prevent other stuck cases.
If you’d like, I can share step-by-step UI instructions to add the “heartbeat missing → Crashed” automation in your local server. Also, which Prefect version are you on and which worker type are you running in the container (e.g., Process worker)?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