@Marvin I have a Flow that has 5 tasks. Within the flow, task three fails. I fix something in the backend that will allow the task to complete. Is there a way in the UI to restart the flow and start at task three? Or do I need to retry the entire flow.

The search in the Prefect documentation didn't return the specific answer to whether you can restart a flow at a specific task from the UI. However, Prefect typically allows for retries and managing task failures, including a variety of retry semantics and self-healing logic. In general, Prefect supports rerunning tasks, but the UI capabilities might have differences. For a definitive answer and perhaps step-by-step guidance, it might be best to search specifically for UI-based task retries or flow restarts in the documentation, or look into the Prefect GitHub issues for related discussions. I can continue searching for you with a more focused approach or you can explore the Prefect concepts page and the blog on task queues for more general information on handling task failures.

@Nate thanks for the link! I think I get it. Using that example provided (where

subflow_1

finishes but

2

crashes), then I would have a "running" result number of 1. Having trouble envisioning how the retry part would function.... would the

main_run

have some sort of

results

input that skips ahead to the right sub flow/task?

the way I think about this is: • runs have a

State

, a

State

might have a

.result()

attached, depending on whether it was persisted via

persist_result=True/False

• retries start from the first non-

Completed

state that has an upstream persisted result so if I have a flow A, B, and C with

retries=1

where all have subflows (or tasks) have

persist_result=True

and I run it, A completes, B and C fail A's result is persisted, so when the flow run retries, it uses the persisted result from A and starts with B if I had not persisted results, it would run all the way through A, B, and C because "no progress was saved"

Ohhhhhhhhhh