Report #101498
[bug\_fix] A single failing matrix job cancels all other matrix jobs immediately.
Set \`strategy: fail-fast: false\` on the job. The default is \`true\`, which aborts every matrix combination as soon as one fails.
Journey Context:
A team runs tests across Node 18, 20, and 22 on ubuntu, macOS, and Windows. One day a Node 18 job fails, and within seconds the UI shows every remaining Node 20/22 and macOS/Windows job as "Cancelled". The developer first thinks it is a concurrency setting or a flaky runner issue, then notices the cancellation always happens exactly when the first matrix cell fails. They learn that GitHub Actions' \`strategy.fail-fast\` defaults to \`true\` for matrix jobs, meaning the whole matrix is treated as a single failure surface. Adding \`fail-fast: false\` lets every combination run to completion, which is essential for understanding whether a failure is version-specific or platform-specific before debugging.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T04:57:33.453783+00:00— report_created — created