@Marvin Here is my custom trigger configuration

{
  "type": "event",
  "match": {
    "prefect.resource.id": "prefect.flow-run.*"
  },
  "match_related": {
    "prefect.resource.id": [
      "prefect.deployment.prod-*",
      "prefect.deployment.dev-sbx-content-update-gdrive-deployment",
      "prefect.deployment.dev-sbx-content-update-feedback-integration-gdrive-deployment"
    ]
  },
  "after": [],
  "expect": [
    "prefect.flow-run.Completed"
  ],
  "for_each": [
    "prefect.resource.id"
  ],
  "posture": "Reactive",
  "threshold": 1,
  "within": 0
}

But it does not match any completed flow run. Can you help me understand why ?

It seems I ran into a hitch while trying to access the Prefect documentation and GitHub issues for your trigger configuration issue. Let me give it another go to uncover information that might help. Please hold on... It looks like there's something discerning in your trigger setup based on the Prefect 3.x documentation I found, even though my attempts to access GitHub issues have failed, possibly due to authorization hurdles. Here's a key point you may consider: 1. Matching and Expectations: Your configuration is attempting to match specific

prefect.resource.id

patterns in both

match

and

match_related

. Ensure that the flow runs you're testing actually conform to these patterns. The

expect

key specifies you're looking for

"prefect.flow-run.Completed"

, so it's important that these events also pass through these

match

filters. 2. Threshold and Timing: The

threshold

is set to 1, which means your trigger needs at least one matching event to fire. Since

within

is set to 0, you're expecting this match immediately. If these conditions aren't met in the exact way expected, the trigger won't activate. You might want to double-check your flow runs to make sure they precisely align with the criteria you've set. Here's a document link that provides more insights into configuring and troubleshooting triggers like yours. If the issue persists, it might be wise to double-check any concurrency settings or priority assignment for your flow runs, possibly affecting trigger timing and completion visibility. If only robots could get tired... I'd definitely need a break after this!