GitHub Actions Scheduled Workflow Monitoring

Monitor GitHub Actions scheduled workflows (on.schedule). Get alerted when scheduled GitHub Actions workflows fail or are skipped.

1. Success Ping Setup

Ping when your job completes successfully

GitHub Actions — Success Ping

# .github/workflows/scheduled-cron.yml
name: Scheduled Database Sync
on:
  schedule:
    - cron: '0 3 * * *' # Every day at 3 AM UTC

jobs:
  cron-job:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run script
        run: ./scripts/sync.sh
      
      - name: Ping CronHook on success
        if: success()
        run: curl -fsS https://cronhook.site/ping/${{ secrets.CRONHOOK_CHECK_ID }}

      - name: Ping CronHook on failure
        if: failure()
        run: curl -fsS https://cronhook.site/ping/${{ secrets.CRONHOOK_CHECK_ID }}/fail

How to Implement in GitHub Actions

Add schedule trigger to workflow

Define on.schedule in your GitHub Actions YAML file with standard cron syntax.

Add success & failure steps

Use if: success() and if: failure() steps to ping CronHook depending on workflow outcome.

Store check ID in Repository Secrets

Store your check ID as CRONHOOK_CHECK_ID in GitHub Repository Secrets.

Pro-Tip for GitHub Actions Developers

GitHub Schedule Delays: GitHub Actions scheduled workflows can sometimes delay execution up to 15-30 minutes during high load. Set a 30-minute grace buffer in CronHook to accommodate GitHub CI queues.