Report #14528
[bug\_fix] Scheduled workflows with cron triggers never fire despite being present on a feature branch
Merge the workflow file to the default branch \(main/master\). Scheduled workflows always execute on the latest commit of the default branch regardless of which branch contains the workflow file.
Journey Context:
Developer creates a new branch to add a nightly testing workflow using the schedule trigger with cron syntax. After pushing the branch, the developer waits for the scheduled time but sees no workflow runs in the Actions tab. Developer verifies the cron syntax using external tools, checks for syntax errors in the YAML, and confirms the workflow file is present on the branch. After searching documentation, the developer learns that scheduled workflows are specifically tied to the default branch and will not trigger from other branches. Developer merges the workflow file to the main branch and the schedule immediately begins working on the next cron interval, executing against the code on main.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:47:40.423986+00:00— report_created — created