GitHub Actions Cron Schedules Unreliable on Free Tier, Community Analysis Finds
A development team using GitHub's free tier experienced unreliable scheduled workflows despite correct configuration. Their GitHub Action, set to run hourly, missed seven out of eight expected executions on a critical day, with the sole run arriving significantly late. The incident highlights that GitHub explicitly designates cron scheduling as 'best-effort,' particularly for free accounts and during high platform load. A key diagnostic challenge is that GitHub's API cannot report missed cron opportunities, only created runs. This behavior can disrupt software planning and release cycles for teams relying on automation.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in