Skip to content

chore: offset crisp-triage cron off the exact hour - #99

Merged
lihsaa591 merged 1 commit into
masterfrom
chore/cron-offset-minute
Sep 29, 2026
Merged

lihsaa591 merged 1 commit into
masterfrom
chore/cron-offset-minute

Conversation

@lihsaa591

Copy link
Copy Markdown
Contributor

Summary

  • Two consecutive scheduled slots (12:00 and 15:00 UTC) never fired at all on 2026-09-29 -- no failed/skipped run logged, just silently absent.
  • Confirmed: workflow is active, YAML valid, cron expression valid -- nothing wrong on our side.
  • Offsets the cron to minute 17 instead of minute 0, matching GitHub's own documented guidance that scheduling at the exact top of the hour increases the chance of delayed/dropped runs due to platform-wide congestion.
  • Not a proven root cause (no access to GitHub's internal scheduler) -- a low-risk mitigation. If the gap recurs on this new offset, that rules this out and points elsewhere.

🤖 Generated with Claude Code

Two consecutive scheduled slots (12:00 and 15:00 UTC) never fired at
all on 2026-09-29 -- no failed/skipped run logged, just silently
absent. Workflow confirmed active, YAML valid, cron expression valid.
Matches GitHub's own documented cause: every scheduled workflow
across GitHub competing for the exact top of the hour is a known
source of delayed/dropped runs. Not a proven root cause (no access to
GitHub's internal scheduler), but a low-risk mitigation per their own
guidance -- if the gap recurs on this new offset, that would actually
rule this out and point elsewhere.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@lihsaa591
lihsaa591 merged commit 7f7f33d into master Sep 29, 2026
2 checks passed
@lihsaa591
lihsaa591 deleted the chore/cron-offset-minute branch September 29, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant