server-status: add daily run after gannet's health report - #2505
Merged
Merged
Conversation
The 15-minute schedule is often skipped for hours, which left the Gannet Dashboard showing the previous day's report. A dedicated 11:15 UTC run lands after gannet_health.sh in both PDT and PST. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BCeigy99PQhoUdfUZXZ9Zj
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.
Why
On 2026-09-28 the Gannet Dashboard kept showing the previous day's report even though
gannet_health.shhad written a new one at 03:00 PDT (10:00 UTC). The*/15schedule had not fired since 06:59 UTC. GitHub scheduled runs are best-effort, and in practice this workflow has been running every few hours instead of every 15 minutes. A manualworkflow_dispatchpicked up the new report right away.Change
Adds a second schedule,
15 11 * * *, to.github/workflows/server-status.yml. Cron is UTC, so 11:15 UTC comes after gannet's 03:00 Pacific run all year (04:15 PDT, 03:15 PST). 10:15 UTC would work in summer but would fall before the report in winter.The 15-minute schedule is unchanged.
Caveat
GitHub can still delay or skip this run. A single daily slot just gives the refresh a better chance than relying on one of the 15-minute runs happening to fire after 03:00. The fully reliable options are the in-network cron described in
scripts/README.mdor having gannet trigger the publish itself.🤖 Generated with Claude Code
https://claude.ai/code/session_01BCeigy99PQhoUdfUZXZ9Zj
Generated by Claude Code