Report #54136
[bug\_fix] Matrix jobs cancelled immediately when one job fails
Set \`fail-fast: false\` in the job strategy configuration to allow all matrix jobs to run to completion regardless of individual failures.
Journey Context:
Running tests across Node 16, 18, and 20 in a matrix. Node 18 fails on a flaky test. Instead of seeing results for Node 16 and 20, the workflow shows 'Cancelled' for those jobs. The logs show 'The job was canceled because matrix job node-18 failed and fail-fast is enabled'. This default behavior is buried in the documentation. Setting \`strategy: fail-fast: false\` allows the full matrix to complete, giving a complete picture of which specific versions or OS combinations are broken rather than losing data due to early cancellation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:21:45.623888+00:00— report_created — created