Rename scheduled trigger copy to scheduled automations

Shola Quadrirequested to merge
639624-rename-scheduled-trigger-strings into master

What does this MR do and why?

This MR addresses #639624 (closed) and renames user facing scheduled trigger copy to scheduled automations.

Background

"Trigger" was renamed to "automation" in user facing copy while the scheduled trigger was still in implementation, so that work landed messages that still say "trigger". The settings, API, and docs layers already moved, which left users seeing both words for one thing.

This moves the strings that were left behind with no behaviour change.

Out of scope

Identifiers keep their names, since renaming them breaks callers: Ai::FlowTrigger, the ai_flow_triggers table, the duo_scheduled_triggers_* columns and the lock_duo_scheduled_triggers_enabled parameter, etc.

Also unchanged, because they belong to a broader event trigger rename rather than this one:

  • The flow_trigger_created, flow_trigger_updated, and flow_trigger_deleted audit event descriptions.
  • The remaining GraphQL "flow trigger" descriptions.
  • The Vue "Trigger" copy still gated on the duo_automations flag.
  • "Flow trigger" and "pipeline trigger" where they appear beside the renamed phrases in the compliance strings.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

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.

Related to #639624 (closed)

Merge request reports