Free tools Windows power users keep installed
One-click scans. No signup required.
GitHub documents that scheduled Actions workflows can start late during periods of high load, especially around the start of an hour; if load is sufficiently high, queued jobs may be dropped. That makes platform load one possible explanation for a late or missing run—not proof of what happened in any particular repository. Check the run history, cron timing, default branch, and workflow state before drawing a conclusion.
What GitHub says about late and missing scheduled runs
GitHub’s workflow troubleshooting documentation says scheduled events can be delayed during periods of high Actions workload. It identifies the start of every hour as a high-load period and says that, when load is sufficiently high, some queued jobs may be dropped. GitHub recommends choosing a different minute of the hour to decrease the chance of delay. This is risk reduction, not a guarantee of punctual execution.
Those documented behaviors make load a plausible explanation for a delayed or absent run. They do not establish that load caused a particular pattern, such as a workflow running late for 30 nights and then missing one. Without the repository’s workflow file and run records, the cause of that specific pattern cannot be determined.
Diagnose the schedule in this order
-
Check whether GitHub created a workflow run
Open the repository’s Actions tab and inspect the workflow’s run history. Compare each run’s creation and start times with the expected schedule. A run that exists but starts late points to a different issue than a date with no run at all. Note the missing dates as well as actual timestamps; do not infer a cause from the pattern alone.
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.#1 Best Overall
-
Move the scheduled minute away from the top of the hour
If the cron expression is set to minute
0, choose another minute within the hour. GitHub specifically identifies the beginning of each hour as a high-load time and recommends scheduling at a different time of the hour. The documentation does not promise an exact start time or say that moving the minute will eliminate delays or dropped events. -
Verify the workflow is on the default branch
A scheduled workflow file must be present on the repository’s default branch. Scheduled runs use the latest commit on that branch, not a version that exists only on another branch. Confirm the current default branch in repository settings and inspect the workflow file there. GitHub documents this requirement in its schedule event documentation and workflow trigger documentation.
-
Check whether the workflow is enabled
GitHub advises checking whether a workflow was manually disabled. In addition, scheduled workflows in public repositories are automatically disabled after 60 days without repository activity, according to GitHub’s workflow enablement documentation. Check the workflow’s status and the repository’s activity history if it is public.
-
Validate the cron expression and time zone
GitHub Actions schedules use POSIX cron. The default time zone is UTC; a schedule can instead specify an IANA time zone. The minimum supported frequency is once every five minutes. If a configured time zone observes daylight saving time and the scheduled time falls in an hour skipped during the spring-forward transition, GitHub advances the run to the next valid time. Check the schedule syntax and the time zone against the time you actually expect, using the schedule documentation.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Keep evidence if the issue continues
Record the workflow YAML from the default branch, repository visibility and recent activity, the intended time and time zone, and the Actions run history—including dates with no run. Preserve relevant available logs. Those details can help distinguish schedule configuration or workflow state from platform-level delay; without them, attributing a particular missed event to load is speculation.
How to interpret the pattern
Repeated late starts followed by one absent run are consistent with more than one possible explanation. High Actions load is documented behavior, but branch placement, disablement, cron syntax, and time-zone assumptions are also concrete checks. The title alone supplies no run IDs, timestamps, workflow YAML, or logs, so it is not enough to verify the delays or identify why a run was missing.
GitHub’s documentation gives qualitative guidance, not a measured delay rate or a probability that a scheduled event will be dropped. Treat the recommendation to avoid the top of the hour as a practical mitigation, not as evidence that a changed schedule will be perfectly reliable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
