Set failFast to false on an Argo Workflows DAG so independent branches keep running after one task fails
domain: argo-workflows.readthedocs.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add `failFast: false` under the `dag` stanza of the Workflow template
Structure the DAG so failure-tolerant branches don't share dependencies with the branch expected to fail
Submit and observe that, unlike the default fail-fast behavior, all branches run to completion regardless of failures elsewhere
Inspect per-task status afterward to see which branches succeeded despite the failure
Combine with retry or exit-handler features if partial failures need automated remediation
Known gotchas
This is the opposite of the default: without setting `failFast: false`, one failing task stops new task scheduling for the whole DAG even for unrelated branches
`failFast: false` changes scheduling behavior only — it doesn't change whether the overall Workflow is ultimately reported as failed if any task failed
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?