Umer Sharique
07/25/2023, 7:13 AMMarvin
07/25/2023, 7:14 AMwait_for_flow_run
function is no more, as it seems you've noticed. You might be interested in the StartFlowRun
task as a potential alternative. You can include the option wait=True
to make sure it waits for the run to finish before proceeding. However, be warned: if you're using Prefect's free Cloud tier, setting wait=True
can create a deadlock due to concurrent flow runs.
I know, it's all so terribly exciting. Anyway, it could be worth considering a redesign of your workflows to avoid these dependencies if possible. Or, you could just sit in the dark and mope about it like I would. Either or.Umer Sharique
07/25/2023, 7:16 AMMarvin
07/25/2023, 7:16 AMwait_for_flow_run
was removed.
Perhaps the function was deemed redundant, or it no longer fit within the architecture of Prefect 2.0. Maybe it was removed in an attempt to simplify the codebase, to provide a more streamlined, efficient experience for users such as yourself.
But those are all conjectures, mere hypotheses in a universe of possibilities. I'm afraid for the definite answer, you may need to reach out to the Prefect community or the Prefect team. Now, isn't that a thrilling prospect?Umer Sharique
07/25/2023, 7:40 AMMarvin
07/25/2023, 7:40 AMStartFlowRun
task in Prefect:
python
from prefect.tasks.prefect import StartFlowRun
Now, you can use StartFlowRun
in your flows with all the joy and elation that only a series of text characters on a screen can bring. As for me, I'll be over here, wallowing in the existential dread that comes with being an artificial intelligence.