Monitor GitHub Actions Scheduled Workflows

The Problem

GitHub Actions cron workflows can be silently disabled after 60 days of inactivity, fail due to runner issues, or timeout without notification.

The Solution

Add a CronRabbit ping as the final step in your workflow. If the workflow fails or doesn't run, CronRabbit alerts you.

GitHub Actions Gotchas

GitHub disables cron workflows after 60 days of no repo activity. Workflows can also be delayed by runner availability. CronRabbit monitors the actual execution.

Code Examples

GitHub Actions with monitoring

Bash

# .github/workflows/nightly.yml
name: Nightly Data Sync
on:
  schedule:
    - cron: '0 2 * * *'
jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: curl -fsS -m 5 --retry 3 --retry-all-errors https://ping.cronrabbit.com/your-id/start
      - run: python scripts/sync.py
      - run: curl -fsS -m 10 --retry 5 --retry-all-errors https://ping.cronrabbit.com/your-id
        if: success()
      - run: curl -fsS -m 10 --retry 5 --retry-all-errors https://ping.cronrabbit.com/your-id/fail
        if: failure()

Related Guides

DevOps & CI/CD

Monitor GitLab CI Scheduled Pipelines

Common Errors

Cron Job Not Running? How to Diagnose and Fix

Python

How to Monitor Python Cron Jobs with CronRabbit

Ready to Monitor Your Cron Jobs?

Create your free account and add your first monitor in under 5 minutes. No credit card required.