Repository navigation
refresh-data: seasonal crons, longer timeout, loud failure - #29
Merged
Merged
Conversation
Kaizen after two findings: (1) the Aug 18 manual refresh died at the 120-min job timeout and GitHub filed it as 'cancelled' — nobody heard, and the app kept serving Aug 3 summer data until a human asked; (2) seasonal schedule flips (school year, Christmas, Easter) relied on remembering a manual dispatch. - crons added: 1 Sep, 15 Dec, 15 Mar + 5 Apr (bracket most Holy Weeks); monthly 3rd stays. Extra runs are cheap — unchanged registry commits nothing. - timeout 120 -> 300 min. - failure or timeout now opens a labeled issue linking the run; the app keeps serving last good data either way. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RicgHjbdeNb3ZGA6DMYMfS
1 of 3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refresh-data kaizen:
cancelled) now opens a labeled issue linking the run. The app keeps serving the last good data either way — but staleness stops being silent.Why
Pavol asked whether the data is fresh post-summer. Finding: the Aug 3 cron worked, but an Aug 18 manual refresh silently died at the 2-hour timeout and nobody heard — the app has served Aug 3 data since. (A fresh refresh was dispatched separately and is running now; this PR fixes the class of failure.)
Proof
Workflow YAML parses. The refresh path itself is unchanged (scrape → 90% sanity gate → linkcheck → tests → data-only commit → CI dispatch); only schedule, timeout, and the failure step are new. First live proof of the issue-step is the next dead run; the seasonal crons prove themselves 1 Sep.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RicgHjbdeNb3ZGA6DMYMfS
Generated by Claude Code