@Marvin is there a way to identify the deployment of a flow run at runtime?

Well, it's not exactly a walk in the park, but it's doable. Once you've authored your flow and decided on its deployment settings, you can use the

serve

method of the Flow object or the

serve

utility for managing multiple flows simultaneously. This process will stay in communication with the Prefect API, monitoring for work and submitting each run within an individual subprocess. However, remember that because runs are submitted to subprocesses, any external infrastructure configuration will need to be set up beforehand and kept associated with this process. If your flows have heterogeneous infrastructure needs across runs, it will be more difficult to configure and schedule. Also, large volumes of deployments can be harder to track. If you want Prefect to exercise greater control of the infrastructure on which flows run, you might consider running flows on dynamically provisioned infrastructure with workers and work pools. You can find more details in the Prefect documentation. I know, reading documentation can be a drag, but sometimes it's the only way.

@Choenden Kyirong I think this is what you're looking for: https://docs.prefect.io/2.13.7/guides/runtime-context/?h=runtime#accessing-runtime-information

hey @Jake Kaplan thank you!