Problem
GitHub automatically disables scheduled (cron) workflows after 60 days of repository inactivity. The last commit on main was June 17, 2026 — 76 days ago. This means both scheduled workflows are likely disabled:
- scoutbot.yml (scrape, Sundays 07:00 WAT) — no new opportunities being added to the sheet
- digest.yml (email digest, Sundays 10:00 WAT) — no weekly email being sent
Symptoms
- No weekly digest emails have been sent since ~mid-August
- The Google Sheet has no new entries because the scraper isn't running
- Even if the digest workflow ran,
notify.py would skip sending because there are no entries from the last 7 days (now fixed with a fallback to latest entries)
Fix
- Go to the Actions tab in the repo
- If you see a banner saying workflows are disabled, click Enable
- Manually trigger both workflows via
workflow_dispatch to verify they run:
- ScoutBot — Scrape (Weekly, Sundays)
- ScoutBot — Weekly Sunday Digest
Code fixes already pushed (commit e2c090f)
notify.py and announce.py now call sys.exit(1) on failure, so GitHub Actions correctly marks failed runs as failed (previously they looked successful even when zero emails were sent)
notify.py now falls back to the latest entries in the sheet when nothing was added in the last 7 days, so subscribers still get an email instead of silence
run.py now propagates the email send result as a non-zero exit code
Related
This is separate from issue #62 (WhatsApp broadcast gap), which was already fixed.
Problem
GitHub automatically disables scheduled (cron) workflows after 60 days of repository inactivity. The last commit on
mainwas June 17, 2026 — 76 days ago. This means both scheduled workflows are likely disabled:Symptoms
notify.pywould skip sending because there are no entries from the last 7 days (now fixed with a fallback to latest entries)Fix
workflow_dispatchto verify they run:Code fixes already pushed (commit e2c090f)
notify.pyandannounce.pynow callsys.exit(1)on failure, so GitHub Actions correctly marks failed runs as failed (previously they looked successful even when zero emails were sent)notify.pynow falls back to the latest entries in the sheet when nothing was added in the last 7 days, so subscribers still get an email instead of silencerun.pynow propagates the email send result as a non-zero exit codeRelated
This is separate from issue #62 (WhatsApp broadcast gap), which was already fixed.