Skip to content

fix: News schedule goes stale when GitHub drops cron runs #363

Open

Description

@DevSecNinja

Problem

news.ravensberg.org showed the previous day's news until a manual dispatch at 13:39Z on 2026-11-17. No briefing had been generated since 2026-11-16 20:17Z.

  • news.yml runs on cron 7 * * * * but only does work when the Europe/Amsterdam hour is odd and between 07 and 21. On 2026-11-17 GitHub fired it only at 03:41Z and 13:05Z, both even local hours, so both were skipped.
  • The hourly news-watchdog.yml (37 * * * *) is meant to catch up, but GitHub fired it only once (04:07Z, outside the active window). A recovery path that relies on another hourly cron fails the same way the primary does.

Fix

Gate on freshness instead of wall-clock parity, inside News itself:

  • Tick every 20 minutes from 05:00 to 20:59 UTC (7,27,47 5-20 * * *), which covers 07:00–21:59 local time in both CET and CEST.
  • Skip ticks outside the local active window.
  • Read the updated_at of the wazzup-state.zip asset on the news-state release (one API call) and generate only when it is at least 100 minutes old. Generations land 100–120 minutes apart.
  • During the morning (07:00–08:59) and evening (20:00–21:59) due windows, also generate when the state is fresh but today's due briefing is missing from the state zip, and pin that kind for generation. Otherwise a run that starts just before a window, or setup that crosses the end of a window, would skip that day's morning or evening briefing.
  • Missing or unreadable state counts as stale.
  • After a failed or timed-out News run, back off 55 minutes before any scheduled generation so a persistent failure doesn't spend AI requests on every tick.
  • Remove the separate news-watchdog workflow, which this replaces.

Skipped ticks finish in seconds without installing tooling. That's 48 short ticks a day, down from 24 News runs plus 24 watchdog runs.

Activity

  1. added
    area/githubGitHub Actions, Renovate, labels, and repository automation
    on Nov 17, 2026
  2. added
    area/dataGenerated data contracts, source config, fixtures, and retention
    on Nov 17, 2026
  3. added a commit that references this issue on Nov 17, 2026
    726d629
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/dataGenerated data contracts, source config, fixtures, and retentionarea/githubGitHub Actions, Renovate, labels, and repository automation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions