Skip to content

fix(fleet): raise dispatch-suite watch cap 75->180 min #394

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joshua-temple merged 1 commit into from
Jun 27, 2026
Merged

fix(fleet): raise dispatch-suite watch cap 75->180 min #394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/actions/dispatch-suite/action.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,11 +110,11 @@ runs:
# This loop retries on transient API errors while still failing closed on
# real run failures and on timeout.
#
# MAX_ATTEMPTS * WATCH_INTERVAL = wall-clock cap (~75 min at 60s each).
# MAX_ATTEMPTS * WATCH_INTERVAL = wall-clock cap (~180 min (3h) at 60s each, headroom for queue+run under full-fleet load, well under GitHub's 6h job cap).
# The 4env suite runs the full lifecycle plus a chained multi-env hotfix
# and the Step 13 conflict probe, each a serial cascade run, so the cap
# must clear its 60-minute internal job timeout with headroom.
MAX_ATTEMPTS=75
MAX_ATTEMPTS=180
CONSEC_ERRORS=0
MAX_CONSEC_ERRORS=5
attempt=0
Expand Down
Loading