Menu

Why GitHub Actions scheduled workflows fail silently (and how to catch them)
📰

Why GitHub Actions scheduled workflows fail silently (and how to catch them)

DEV Community: cicd·Yağız Yorulmazlar·about 14 hours ago
#1XQSdfua
#devtocicd#devto#dev#github#runs
Long article (871 words) — no AI summary yet.
Reading 0:00
15s threshold

If you run backups, database cleanups, or report syncs with GitHub Actions on: schedule , it is easy to assume GitHub will email you when something breaks.

It will, if the workflow actually starts and exits with an error.

The harder failure mode is when the workflow never runs at all. There is no failed job, no red X, and no email. You only find out weeks later when you go looking for a backup that stopped existing last month.

Three ways on: schedule goes silent

1. The 60-day inactivity auto-disable

In a public repository, GitHub automatically disables scheduled workflows if there has been no repository activity for 60 days. Utility repos (like a standalone backup or data-sync repo) hit this constantly. You push a working workflow, leave it alone because it works, and two months later it quietly stops running.

2. Best-effort scheduling and dropped runs

GitHub treats on: schedule as best-effort.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.