GitHub Actions scheduled workflow monitoring

Know when a scheduled GitHub Actions workflow goes silent

A scheduled workflow can miss a trigger, fail before completion, or stop running without a useful alert. QuietPulse watches for the success heartbeat you expect and alerts you through Telegram or webhooks when it never arrives.

Create a free monitorRead the docs

Why GitHub notifications are not enough

Failure notifications help after a run starts. They cannot reliably warn you about a workflow that never starts. Heartbeat monitoring checks the outcome that matters: did the scheduled work finish on time?

Catch missing triggers

Detect silence when a scheduled workflow never starts.

Ping after success

A heartbeat confirms the important work reached completion.

Alert where you work

Receive Telegram alerts or route incidents through webhooks.

Set it up in three steps

  1. 1. Create a monitored job. Match its interval and grace period to your scheduled workflow.
  2. 2. Store the full ping URL. Add it as the QUIETPULSE_PING_URL repository secret.
  3. 3. Ping only after success. Add the QuietPulse action as the final workflow step.
.github/workflows/nightly-sync.yml
name: Nightly sync

on:
  schedule:
    - cron: '0 2 * * *'
  workflow_dispatch:

jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run sync
        run: ./scripts/sync.sh
      - name: Send heartbeat to QuietPulse
        if: success()
        uses: vadyak/quietpulse-actions@v1
        with:
          ping_url: ${{ secrets.QUIETPULSE_PING_URL }}

Related guides

GitHub Actions schedule not triggering

Debug common causes of silently missed schedules.

GitHub Actions monitoring guide

See complete examples and heartbeat best practices.

Cron job monitoring guide

Learn the heartbeat model, grace periods, and alert routing.

QuietPulse vs Healthchecks.io

Compare heartbeat monitoring options before choosing a tool.

FAQ

How do I monitor a GitHub Actions scheduled workflow?

Send a heartbeat after successful completion. QuietPulse alerts you if the expected ping does not arrive.

Can scheduled workflows miss runs?

Yes. Schedules can be delayed, disabled, misconfigured, or fail before completion. A missing heartbeat makes the silence visible.

Should the heartbeat run at the start or end?

Send it at the end with if: success() so the ping represents successful completion.

Start monitoring scheduled workflows

Create your first monitor for free, then add a single action step to the workflows that matter.

Start freeView pricing