@Marvin, can I use a negation on matched events to trigger flows? use case: trigger something at every event of run flows, except itself

To answer your question about using negation on matched events to trigger flows in Prefect, I'll need to check the Prefect documentation and any related GitHub issues. But first, can you confirm which version of Prefect you are using (e.g., Prefect 2.x or 3.x)? This will help tailor the solution to your specific version.

@Marvin 3.x

In Prefect 3.x, it seems you can configure event-based triggers with certain conditions but directly negating specific events from triggering flows might require more creative configurations. Custom triggers allow you to define which events should influence the automation of workflows. You can use parameters like

"match"

and

"match_related"

to specify relevant events, and configure these to include or exclude certain event types based on specific criteria. For compound triggers, the

require

parameter allows for the specification of conditions such as any event out of many triggering the flow. However, the documentation does not explicitly mention a negation feature for excluding specific events. From what I found, you might be able to work around this by using the combination of filters and conditions, but direct negation isn't specifically noted. For a deeper approach or assistance, I would recommend engaging with the Prefect community or support. You can explore more about custom triggers and event-based automations in the Prefect documentation: https://docs-3.prefect.io/3.0/automate/events/custom-triggers.