## Summary Beta is the public release of scheduled triggers. They become available to users who have turned on experiment and beta features, and groups and projects can turn them off. Target milestone: 19.6. ## In scope - Scheduled triggers are only available when experiment and beta features are turned on: gitlab-org/gitlab#634138. - Settings in groups and projects to turn off scheduled triggers: gitlab-org/gitlab#634139. - Rebrand Triggers as Automations: gitlab-org&23940. This renames "Triggers" to "Automations" in all user-facing copy and rebuilds the Automations page and details panel. It is behind its own feature flag, enabled by default in the same release that makes scheduled triggers available to external users. - Permission checks and input restrictions: gitlab-org&23984. - Users can't create a scheduled trigger, or change its flow, so that it runs with more access than their own. - The trigger description is no longer used as the flow goal. - Scheduled triggers have no goals. - External agents and `config_path` triggers can't use the scheduled event type. - The UI and docs explain how scheduled triggers run: dedicated account, role, no composite identity. - The audit event records before and after values. - Documentation: - Scheduled trigger docs, including limits such as schedules per project: gitlab-org/gitlab#632922. - Troubleshooting docs for the "Flow enabled without a trigger" warning: gitlab-org/gitlab#632653. - Replace the hour text input with a listbox: gitlab-org/gitlab#630548. - Enable the `ai_flow_schedules` feature flag by default, with the beta gate still applying: gitlab-org/gitlab#627751. ## Out of scope (GA or later) - User-selectable role for the trigger's service account: gitlab-org/gitlab#628995. Review said this is fine to skip while the feature is opt-in, but it is needed before GA. - SA+SA composite identity: gitlab-org/gitlab#617178. - Removing the beta gate. - Feature flag removal. - Remaining load protections, such as rate limits and a circuit breaker. ## Open questions - The group and project settings (gitlab-org/gitlab#634139) are new scope and need an estimate. They may put the 19.6 target at risk. - How do the group and project settings interact? Does a group setting apply to its subgroups and projects? Can a project override it? ## Exit criteria - Scheduled triggers are available to external users who have turned on experiment and beta features. - Group and project settings can turn scheduled triggers off. - The `ai_flow_schedules` flag and the rebrand flag are on by default in the same release. - The permission checks from gitlab-org&23984 are in place. - Docs are published. ## Related - Parent epic: gitlab-org&22284 - Customer Zero epic: gitlab-org&23872 - GA epic: gitlab-org&23873 - Rebrand Triggers as Automations: gitlab-org&23940 - Permission checks and input restrictions: gitlab-org&23984