Show all triggers for a configured flow

Austin Regneryrequested to merge
aregnery/fix-triggers-config-connection into master

What does this MR do and why?

When viewing an enabled flow, the Triggers section links a flow to its trigger configuration. It only showed one trigger even when several were configured, so the page did not tell the full story.

References

No related issue. Asking a reviewer to confirm whether multiple triggers per flow is intended behavior.

Screenshots or screen recordings

Before After
CleanShot_2026-08-11_at_09.59.56_2x CleanShot_2026-08-11_at_10.10.08_2x

How to set up and validate locally

  1. Enable the Duo Agent Platform and open a project's flows page at /<namespace>/<project>/-/automate/flows.
  2. Configure a flow, then add a second trigger for the same flow so the consumer has more than one Ai::FlowTrigger row.
  3. Open the flow. Before this change, only one trigger appears in the Triggers section. After, every configured trigger appears, each with its own Edit link.

Multiversion compatibility

This MR changes GraphQL backend and frontend together. On GitLab.com the backend deploys before the frontend, and the frontend reads flowTriggers defensively (falls back to an empty list), so the canary window degrades to the existing empty state rather than erroring.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Austin Regnery

Merge request reports