@Marvin "Trigger a downstream deployment with an event" doesnt's work

It seems you're facing issues with triggering a downstream deployment with an event in Prefect. This could be related to the way Prefect handles templating and event triggers. Here's what I found: 1. Event Triggers: Prefect allows you to schedule a downstream deployment when an upstream deployment completes. You need to start the serve process to listen for scheduled deployment runs and then run the upstream deployment to see the downstream deployment kick off. You can inspect raw events in the event feed in the UI to match related resources. More details can be found here. 2. Issues with Templating: There is an open issue related to lazy templating for deployments in

prefect.yaml

. This affects how template variables, such as

{{ event.resource... }}

, are evaluated. Currently, they are evaluated at deploy time, which might not allow for dynamic changes at runtime. You can track this issue and potential enhancements here. If your problem persists, you might want to explore whether your Prefect version has any known issues or consider using a workaround by explicitly managing event triggers and parameters in your flow definitions. If you have more specific details about your setup or error messages, feel free to share them for further assistance.