Selecting "Automate" from a flow-run.<state change> event in the UI creates a misleading automation trigger form

[taylor-curran]

Bug summary

Select a flow-run.Completed event from the events feed -> click the three dots -> Automate

This produces an automation form with the "Flow run state" trigger type, visually implying the created automation will trigger whenever the flow that produced the completed event enters the Completed state. However, the actual JSON looks like this, indicating a filter on a particular flow run:

{
  "type": "event",
  "match": {
    "prefect.resource.id": "prefect.flow-run.515ea7fa-b6b2-4501-ac85-3bbddbcda043"
  },
  "match_related": {
    "prefect.resource.role": "flow",
    "prefect.resource.id": "prefect.flow.be9d20b8-9db5-4239-a687-906d630ea0fb"
  },
  "after": [],
  "expect": [
    "prefect.flow-run.Completed"
  ],
  "for_each": [
    "prefect.resource.id"
  ],
  "posture": "Reactive",
  "threshold": 1,
  "within": 0
}

Consequently, this automation would only fire if the same flow run emitted another completed event.

Version info

this is in the cloud ui

Additional context

The ability to grab the JSON from the UI is commonly used to help users build their first deployment trigger. The fact that this is wrong affects many beginners.

[cicdw]

@taylor-curran this looks correct to me because you specified that the trigger applies specifically to the flow "a-subflow"; if you remove that I think the match_related field will be empty.

[kevingrismore]

@cicdw I've updated the issue title and description to reflect what I believe was the intent of the issue

[cicdw]

Ooooo gotcha gotcha, yea it's over-specified I see - thank you!