Monitor GitHub Actions Scheduled Workflows

What this guide covers

This guide focuses on detecting skipped or failed scheduled workflow runs that would otherwise stay inside the CI system. The goal is to make the operating decision clear before a stressful incident forces the team to improvise.

• Scheduled runs can be silently skipped or queued late.
• Call the heartbeat from the final successful step only.
• A buffered interval avoids false alarms from queue latency.

How Sandglass supports the practice

Store the heartbeat URL as a repository secret and call it from the final successful step of the scheduled workflow. Sandglass supports the continuous side of this work with checks, incidents, alert routing, and public status visibility.

• Back the practices here with HTTP, ping, TCP, content, SSL certificate, and heartbeat checks.
• Route incidents to email, Slack webhook channels, and generic webhooks so the right people respond fast.
• Use a public status page to keep customers informed while the team works the incident.

Common mistakes to avoid

Scheduled workflows can be skipped or delayed. Add a buffer to the heartbeat interval so normal queue latency does not create false incidents.