Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

We recently updated an automation to use <https://docs.prefect.io/latest/concepts/automations/#composite-triggers|composite-triggers> in order to send out a Pager Duty incident, and we're seeing a change in behavior. :thread:

image.png

Our previous trigger was:
```{
  "type": "event",
  "match": {
    "prefect.resource.id": "prefect.flow-run.*"
  },
  "match_related": {
    "prefect.resource.id": [
      "prefect.tag.tag1",
      "prefect.tag.tag2"
    ],
    "prefect.resource.role": "tag"
  },
  "after": [],
  "expect": [
    "prefect.flow-run.TimedOut",
    "prefect.flow-run.Crashed",
    "prefect.flow-run.Failed"
  ],
  "for_each": [
    "prefect.resource.id"
  ],
  "posture": "Reactive",
  "threshold": 1,
  "within": 0
}```
With an action that looks like what's shown in the screenshot; previously, the PD incidents it created had a title like shown in the screenshot.

We've since updated to the composite trigger:
```{
  "type": "compound",
  "triggers": [
    {
      "type": "event",
      "match": {
        "prefect.resource.id": "prefect.flow-run.*"
      },
      "match_related": {
        "prefect.resource.id": [
          "prefect.tag.tag1"
        ],
        "prefect.resource.role": "tag"
      },
      "after": [],
      "expect": [
        "prefect.flow-run.TimedOut",
        "prefect.flow-run.Failed",
        "prefect.flow-run.Crashed"
      ],
      "for_each": [
        "prefect.resource.id"
      ],
      "posture": "Reactive",
      "threshold": 1,
      "within": 0
    },
    {
      "type": "event",
      "match": {
        "prefect.resource.id": "prefect.flow-run.*"
      },
      "match_related": {
        "prefect.resource.id": [
          "prefect.tag.tag2"
        ],
        "prefect.resource.role": "tag"
      },
      "after": [],
      "expect": [
        "prefect.flow-run.TimedOut",
        "prefect.flow-run.Failed",
        "prefect.flow-run.Crashed"
      ],
      "for_each": [
        "prefect.resource.id"
      ],
      "posture": "Reactive",
      "threshold": 1,
      "within": 0
    }
  ],
  "require": "all",
  "within": 0
}```
same action, same notification block, however the PD incident now look like what's shown in the screenshot. That is, it doesn't look like the body of the Action is getting the jinja vars materialized?

Thanks <@U02A2MYGML0> - this does seem to be a regression - sorry about that! Would you mind filing an issue <https://github.com/PrefectHQ/prefect/issues/new/choose|here> and we can get this fixed asap?

<https://github.com/PrefectHQ/prefect/issues/12766>