@Marvin my event triggered deployments (triggered from flow state changes of another deployment) stopped triggering after updating both the source and triggered flows to Prefect 3. Why is this?

It seems your issue with event-triggered deployments in Prefect 3 might be due to changes in how deployment triggers are configured. Prefect 3 introduces a new events & automations backend, which may require adjustments in your deployment configuration. 1. Deployment Triggers: In Prefect 3, deployment triggers are defined in

prefect.yaml

or through Python using classes like

DeploymentEventTrigger

. Ensure your triggers are correctly defined as per the new configuration methods. Learn more here. 2. Upgrade Considerations: Prefect 3 maintains compatibility with most Prefect 2 workflows, but there are some caveats. For example, agents are replaced by workers, and work pools replace infrastructure blocks. Ensure your workflow aligns with these changes. Upgrade details. 3. Common Gotchas: Be aware that Prefect 3 uses Pydantic 2, and server data from Prefect 2.x is not compatible with 3.x. Also,

Deployment.build_from_flow()

is removed; you should use the new method for deployment creation. Review your deployment configurations and ensure they are updated to align with Prefect 3's new features and requirements.