A scheduled GitHub Actions workflow can start late or, during sufficiently high load, have its queued run dropped. But silence is not proof of a platform issue: a disabled workflow, a schedule missing from the default branch, or a UTC or daylight-saving-time mismatch can produce the same symptom. Check those configuration causes first, then move the schedule away from minute zero and monitor later runs.
What “silent” can mean
There are several different outcomes behind a missed expected run:
As an Amazon Associate I earn from qualifying purchases.
- Delayed: GitHub says scheduled events can be delayed when Actions workflow-run load is high.
- Dropped: GitHub says some queued jobs may be dropped if load is sufficiently high.
- Disabled or ineligible: The workflow may have been manually disabled, may not be on the default branch, or—if the repository is public—may have been automatically disabled after prolonged inactivity.
- Scheduled for another time: The cron expression may be interpreted in UTC rather than the timezone you expected, or daylight saving time may affect the local clock time.
GitHub documents the possibility of delay and dropped queued jobs, but does not publish a rate of missed schedules, a typical delay duration, or a service-level guarantee for scheduled-run timing. The documentation also does not quantify any effect on developer productivity. A silent run can disrupt a team’s process, but the available documentation does not establish how often that happens or measure its performance impact. GitHub Docs’ troubleshooting guidance and its workflow event reference describe the behavior and configuration rules.
Recommended Free Tools
Check the workflow before blaming load
- Confirm it is enabled. Check that the workflow has not been manually disabled. GitHub lists workflow enablement and the configured
on:events among the initial troubleshooting checks. See GitHub’s workflow troubleshooting guidance. - Check the default branch. A
scheduleevent only triggers when the workflow file is on the repository’s default branch. Scheduled runs use the latest commit on that branch, not an arbitrary feature branch. GitHub documents this requirement for the schedule event. - For a public repository, check inactivity. GitHub automatically disables scheduled workflows in public repositories after 60 days without repository activity. Treat this as a documented product rule, not as evidence that Actions load caused the missed run. The event reference describes the 60-day rule.
- Verify the cron expression and timezone. GitHub uses POSIX cron syntax. By default, schedules are interpreted in UTC; a timezone can also be specified using an IANA timezone. The minimum supported interval is once every five minutes. See the workflow syntax reference.
- Account for daylight saving time. When a timezone observes daylight saving time and a scheduled local time falls in the skipped spring-forward hour, GitHub advances the run to the next valid time. GitHub documents this schedule behavior.
Why the minute matters
The start of each hour is a high-load period for GitHub Actions. GitHub warns that scheduled events can be delayed during periods of high workflow-run load and that some queued jobs may be dropped if load is sufficiently high. Its stated mitigation is to choose a different minute of the hour. This can decrease the chance of delay; it does not guarantee punctual execution or prevent every dropped run. GitHub’s troubleshooting page explains the load warning.
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
For example, if a workflow currently runs hourly at minute zero, changing its cron minute to 17 moves it away from the top of the hour:
on:
schedule:
- cron: '17 * * * *'This is an hourly schedule at minute 17, not a guarantee that each run will begin precisely then. Confirm that the expression matches the intended cadence and timezone before committing it to the default branch.
Rank #2
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- Includes Pre-Loaded 32GB EVO+ Micro SD Card (Class 10), USB MicroSD Card Reader
- CanaKit Premium High-Gloss Raspberry Pi 4 Case with Integrated Fan Mount, CanaKit Low Noise Bearing System Fan
- CanaKit 3.5A USB-C Raspberry Pi 4 Power Supply (US Plug) with Noise Filter, Set of Heat Sinks, Display Cable - 6 foot (Supports up to 4K60p)
- CanaKit USB-C PiSwitch (On/Off Power Switch for Raspberry Pi 4)
What to do when the checks pass
- Move a top-of-hour schedule to a different minute, following GitHub’s recommendation.
- Watch subsequent expected runs and record whether each starts late, does not appear, or runs at an unexpected local time. These outcomes point to different causes.
- If the workflow remains enabled, is on the default branch, and has a valid schedule, use GitHub’s troubleshooting guidance to continue investigating. Do not treat one missed run as proof of a systemic outage; the documentation does not provide a frequency baseline against which to judge it.
When a schedule is the wrong trigger
A schedule is appropriate when work should recur on a cadence and can tolerate timing variation. If work should start because a specific repository event occurred, configure a workflow for that event instead of using a clock-based schedule. If a person needs to start a run on demand, a manually dispatched workflow may fit better. GitHub documents these trigger types, but the cited documentation does not compare their reliability. Choose based on what should cause the work to run, not on an unsupported assumption that one trigger is inherently more dependable. See GitHub’s event reference.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Best Value
- 【What you Get】You will get 1*Pi 5 8GB Single Board,1*RasTech Case,1*Active Cooler,1*Screwdriver,1*Installation instructions,12-month free warranty, lifetime service, 24-hour prompt and friendly response.
- 【More Connectors】There are two USB 3.0 ports(5Gbps simultaneously) and two USB 2.0 ports, which triple total bandwidth ,support any combination of up to two cameras or displays. Peak SD card performance is doubled through support for the SDR104 high-speed mode. It provides a smooth desktop experience for you. Offer Gigabit Ethernet and a PCIe interface, along with dual-band Wi-Fi and Bluetooth 5.0/BLE wireless capability. The RasTech Pi 5 Kit use the new 27W 5.1V 5A USB-C power connector.
- 【 Support Dual 4Kp60 Display 】Each of the two microHDMI sockets can control a 4K display at 60 Hertz, now support HDR, offering super HD video for media streaming projects. RPi 5 is the first RPi model that comes with a PCI Express port (PCIe 2.0 x1 with 500 MB/s) to attach SSDs (requires separate M.2 HAT).
- 【 Excellent Chips And Applications】Pi 5 is a full-size Pi computer using silicon built in-house at Pi. The RP1 “southbridge” provides the bulk of the I/O capabilities for Pi 5. Pi 5 is more friendly and convenient in the development of Internet of Things, Web development, machine identification, automatic control and other electronic equipment applications and network.
- 【 Faster CPU, Better GPU 】 Pi 5 features a Broadcom BCM2712 64-bit quad-core Arm Cortex-A76 processor running at 2.4GHz, it delivers a 2–3× increase in CPU performance relative to RaspberryPi 4. The 800MHz VideoCore VII GPU is compatible to OpenGL ES 3.1 and Vulkan 1.2, substantial uplift in graphics performance. Pi 5 Offers lightning-fast CPU speed, a PCI Express interface, a Real Time Clock (RTC) and a power button and runs significantly cooler than Pi 4.
Rank #4
- Fully assembled for plug-and-play operation
- Includes Raspberry Pi 5 with 8GB RAM
- 256 GB PCIe Pi NVMe SSD (Pre-loaded with Pi 64-Bit OS)
- M.2 HAT+
- CanaKit Turbine Black Case for the Pi 5
Rank #3
- Not including the Raspberry Pi 5 (8GB), the Crowpi advanced version comes with the Raspberry Pi 5
- ELECROW Black Case for the Raspberry Pi 5, CrowPi is equipped with a 9-inch HD touchscreen along with a camera; All the regular components used in DIY electronics are packed into the CrowPi development board, such as LCD, LED matrix, buzzer, light sensor, PIR sensor, ultrasonic sensor, IR sensor, etc
- Raspberry Pi Sensors: The Crowpi raspberry pi 5 programming kit is jam-packed with lots of buttons such as 19 different sensors in a tidy easy to use package; You don't have to wait and wire things
- Build Quality: Solid ABS shell and well made components in one place make it strong and convenient to travel
- Programming Lessons: This raspberry pi 5 learning kit ships with step by step instructions and provides 21 lessons to take you through identifying components reading code and running it in the terminal
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.
