ci: add retry job to refresh cron workflows#393
Open
matheus1lva wants to merge 1 commit intomainfrom
Open
Conversation
Adds a `refresh_retry` job that runs on failure to handle transient GitHub infra errors (e.g. action download failures). A final `notify` job consolidates Uptime Kuma reporting based on either attempt's result. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
murderteeth
requested changes
Apr 22, 2026
Contributor
murderteeth
left a comment
murderteeth
left a comment
There was a problem hiding this comment.
- why are we using retries? what evidence motivated this
- the original issue suggests it may be a timing issue. is that theory wrong?
- why aren't historical workflows monitored?
Collaborator
Author
|
At the time of the report it was a random github failure, it was exitting during setup phase, not on any timeout or anything similar - But as i looked again, the reports are failing and apparently that is a timing thing. The initial intent remains, there's nothing to do because of github failing - now im gonna check the other ones. |
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.
Summary
refresh_retryjob to each refresh workflow (lists, snapshot, timeseries, reports, and both historical variants) that runs only when the primaryrefreshjob fails. This absorbs transient GitHub infra failures like action-download errors (e.g.Failed to download archive '.../oven-sh/setup-bun/...').notifyjob so success/failure is based on whether either attempt succeeded, instead of firing from the primary job that just failed.Test plan
Trigger
refresh-listsmanually and confirm only therefreshjob runs on success```
gh workflow run refresh-lists.yml
gh run list --workflow=refresh-lists.yml --limit 1
```
Expected: single run with
refresh+notifyjobs, no retry job executed.Simulate failure (temporarily break the refresh command on a test branch) and confirm
refresh_retryruns```
gh workflow run refresh-lists.yml --ref
gh run view
```
Expected:
refreshfails,refresh_retryruns,notifyreports based on retry result.Verify Uptime Kuma gets exactly one status update per workflow run (no duplicates from both attempts reporting)
🤖 Generated with Claude Code