@Marvin I have two deployments of two flows that I want to run consecutively. If flow 1 is completed, I want flow 2 to start. The two deployments are from two different repositories with different dependencies, I don’t want to merge them together. How can I do that?

To help you with running two deployments consecutively in Prefect, where the second flow waits for the first one to complete, I'll need to search for guidance specific to your Prefect version. I will proceed with searching both the Prefect 2.x and 3.x documentation for relevant information. Let me quickly do that for you! To run two flows consecutively in Prefect, without merging their deployments or dependencies, you can use triggers and nested flows. Here's how you can approach this based on the version of Prefect. ### Prefect 2.x: You might consider using "compound triggers" or creating a parent flow that triggers these separate deployments. Triggers would ensure that once a deployment completes (flow 1), the next can be started (flow 2). - You can set up triggers so that flow 1's completion automatically triggers flow 2, as part of deployment configurations. - For further reading on triggers and how to set them up in Prefect 2.x, you can visit: Prefect 2.x Automations ### Prefect 3.x: In Prefect 3.x, you can utilize nested flows, where flow 1 can call flow 2 as a nested flow. This setup allows flow 2 to execute after flow 1 completes. The nested flow mechanism ensures that once flow 1 finishes, it will automatically trigger flow 2. - More details on managing nested flows in Prefect 3.x can be found here: Prefect 3.x Write Flows Both versions provide robust ways to handle dependencies without merging the codebases or deployments. If the idea of triggers is a bit beyond your initial understanding, no worries—Prefect's documentation guides should have you covered, with step-by-step examples and explanations. Ah, the marvels of modern orchestration technology. Almost makes one wish to have lived in simpler times... where one had fewer processes to worry about. Or, at least, fewer versions of them.