docs: document GCP Batch infrastructure retry for Fusion Snapshots#1640
Open
justinegeffen wants to merge 6 commits into
Open
docs: document GCP Batch infrastructure retry for Fusion Snapshots#1640justinegeffen wants to merge 6 commits into
justinegeffen wants to merge 6 commits into
Conversation
The Fusion Snapshots retry docs only covered Spot reclamation and errorStrategy. Google Cloud Batch surfaces a range of infrastructure failures as exit codes 50001-59999, and by default only 50001 is auto-retried. On Spot-based snapshot runs this leads to avoidable failures. Add a "Retrying Google Cloud Batch infrastructure failures" subsection to the snapshots advanced-configuration page documenting the exit-code range, how to extend google.batch.autoRetryExitCodes, and why errorStrategy on task.exitStatus is unreliable for these codes. Add a pointer from the GCP snapshots page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
❌ Deploy Preview for seqera-docs failed. Why did it fail? →
|
justinegeffen
added
3. Dev/PM/SME reviews complete
justinegeffen
commented
Jul 9, 2026
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
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
3 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.
Jira: EDU-1143
What
The Fusion Snapshots retry documentation only covered Spot reclamation (exit code
50001) anderrorStrategy. Google Cloud Batch surfaces a broader set of infrastructure failures as exit codes in the50001–59999range, and by default only50001is auto-retried. On Spot-based snapshot runs, the other codes cause avoidable failures, and this configuration requirement was undocumented.Changes
fusion_docs/guide/snapshots/configuration.md: add a "Retrying Google Cloud Batch infrastructure failures" subsection under Retry handling — the exit-code range table, how to extendgoogle.batch.autoRetryExitCodes(withmaxSpotAttempts), guidance on which codes to retry, and a note on whyerrorStrategykeyed ontask.exitStatusis unreliable for these codes.fusion_docs/guide/snapshots/gcp.md: add a one-line pointer from the GCP snapshots page to the new section.Verification
Confirmed against the current Nextflow source (
nf-google, v26.04.3):google.batch.maxSpotAttemptsplusgoogle.batch.autoRetryExitCodes(default[50001]); Fusion Snapshots set a non-zeromaxSpotAttemptsautomatically.>= 50000are read from the task exit file, soerrorStrategyconditions ontask.exitStatusdo not reliably match infrastructure codes — hence theautoRetryExitCodes-first guidance.🤖 Generated with Claude Code