Skip to content
QuickStatus.dev

Monitor scheduled GitHub Actions workflows

A scheduled workflow that never starts can't send a failure email. GitHub only tells you about runs that happened. A heartbeat check covers the rest: the workflow pings QuickStatus.dev at the end of each scheduled run, and if the ping doesn't arrive on time, you get an alert.

Get started free Read the checks docs

Why scheduled workflows stop

These come from GitHub's own docs:

  • In a public repository, scheduled workflows are turned off automatically after 60 days with no repository activity.
  • Scheduled runs can be delayed when GitHub is busy, especially at the start of each hour, and some queued runs may be dropped.
  • Schedules are off by default in a forked public repository.
  • A scheduled workflow can stop if the account it runs as is suspended, deleted or deprovisioned.

None of these turns the Actions tab red. The run just doesn't exist.

Set it up

  1. In QuickStatus.dev, click Add check, then Heartbeat. Name it after the workflow, for example “nightly-sync”.
  2. Pick Expected every to match the schedule, for example 1 day for a daily workflow. The shortest is 5 minutes on Free, which is also the shortest schedule GitHub allows.
  3. Pick Grace to cover a late start plus the job's normal run time, for example 1 hour for a daily workflow. GitHub delays are normal, so don't set it too tight.
  4. Copy the ping URL (it's shown only once) and save it as a repository secret named QUICKSTATUS_PING_URL.
  5. Add the two steps below to the end of the job.
name: Nightly sync
on:
  schedule:
    - cron: "17 3 * * *"
  workflow_dispatch:

jobs:
  sync:
    runs-on: ubuntu-latest
    timeout-minutes: 30
    steps:
      - uses: actions/checkout@v4

      - name: Run the job
        run: ./scripts/sync.sh

      - name: Heartbeat
        if: success() && github.event_name == 'schedule'
        run: curl -fsS -m 10 --retry 3 "${{ secrets.QUICKSTATUS_PING_URL }}"

      - name: Report failure
        if: failure() && github.event_name == 'schedule'
        run: curl -fsS -m 10 --retry 3 "${{ secrets.QUICKSTATUS_PING_URL }}/fail"

The github.event_name == 'schedule' condition means a manual run from the Actions tab doesn't ping. That way a working manual run can't hide a schedule that stopped firing. Minute 17 instead of 0 keeps the run away from GitHub's busiest moment. timeout-minutes stops a hung job from running for hours.

Workflows with several jobs: put the heartbeat in a final job with needs: on all the others, so it only pings when every job succeeded.

What it catches

  • A schedule GitHub turned off after 60 days of inactivity
  • A run that GitHub delayed past your grace period or dropped
  • A cron line that was edited or removed on the default branch
  • A job that failed, reported with /fail
  • A job that hung until timeout-minutes cancelled it

Pricing

The Free plan gives you 10 checks of any type, heartbeats included, plus email and Telegram alerts (2 chats) and 14 days of results, with no card needed. Pro is $15 a month for 25 checks, a 1-minute minimum for Expected every, 90 days of results, and Slack, Discord, PagerDuty, Pushover, webhook and unlimited Telegram alerts. See pricing

Check what your cron line means, and see it as a GitHub Actions snippet, with the cron expression generator. For other schedulers, see cron job monitoring.

GitHub Actions cron FAQ

Why didn't my scheduled GitHub Actions workflow run?

The most common reasons are a public repository with no activity for 60 days, a busy period when GitHub delayed or dropped the run, or a fork where schedules are off by default. GitHub doesn't send an alert for a run that never started.

Does GitHub notify me when a scheduled workflow is disabled?

Not with a failed run, because there's no run. A heartbeat check notices the missing ping and alerts you.

What time zone does the schedule use?

UTC, unless you add a timezone with an IANA name such as “Europe/Berlin” under the cron line.

How often can a scheduled workflow run?

At most every 5 minutes. That matches the 5-minute minimum for Expected every on the QuickStatus.dev Free plan.

Where do I keep the ping URL?

In a repository secret. Anyone with the URL can send pings, so keep it out of the workflow file and logs.

Can I monitor a weekly workflow?

Not yet. Expected every goes up to 1 day, so heartbeat checks fit workflows that run at least once a day.