Out of curiosity, is there a "Wait for user" task at all? Im thinking like how in other pipelines you can wait for the user to hit "go" or similar if some checks need to be done before proceeding with a transaction/deployment/rollout, etc

Would pausing a flow run help you? https://docs.prefect.io/2.10.18/concepts/flows/?h=pause#pause-a-flow-run

Hmm, not too much. Here's the use case we're exploring now. 1. Really long, painful set of tasks. Like a bunch of ETL, exporting db shapshot, etc. 2. Pause with the results of that task done 3. Wait for a user to press okay, signifying this is a time when the platform can be updated 4. then run the quick task that uses that results from (1) to modify production data

I think it's the same thing? Calling

pause_flow_run

pauses your flow run until a user presses resume from the UI at which point the run resumes. So you would: 1. Run your initial tasks 2. Call pause_flow_run - the run is paused 3. A user presses resume in the UI - the flow runs resumes 4. Your other tasks are run Or am I missing something there?

Oh youre right, you dont have to set the timeout do you, yeah, that would work great! I see the default is 300s, but I assume a 0 value means "indefinitely"?