@Marvin does executing sub flows via run_deployment in prefect 3 using a self hosted cloud run v2 worker and work pool by default create a new cloud run job for the sub flow? Or does the sub flow run in process?

In Prefect 3.x, when using a self-hosted Cloud Run V2 worker and work pool, running subflows via

run_deployment

typically creates a new cloud run job for each subflow rather than running them in-process. This means that each subflow will be executed in its own isolated environment as a separate cloud run job, providing first-class observability within the Prefect UI and Prefect Cloud. For in-depth customization and management of such deployments, it's possible to configure the base job template of your work pool, influencing how infrastructure is provisioned for these flow runs. For more details on configuring Cloud Run workers and running nested flows, you can refer to the GCP Worker Guide and Writing Flows documentation.