GitHub Actions continue-on-error did not propagate the step outcome
continue-on-error makes a failed step report success as its conclusion, so subsequent steps that check conclusion run as if nothing failed. The real result lives in steps.<id>.outcome, not conclusion.
What this error means
A step that should be treated as failed is treated as passed downstream, because continue-on-error rewrote its conclusion to success.
github-actions
# 'if: steps.lint.conclusion == failure()' never fires
steps.lint.outcome: failure
steps.lint.conclusion: success # rewritten by continue-on-errorCommon causes
Checking conclusion instead of outcome
continue-on-error sets conclusion to success while leaving outcome as failure; conditions must read outcome to detect the real result.
How to fix it
Gate on steps.<id>.outcome
- Give the optional step an id.
- In downstream conditions, reference steps.<id>.outcome to detect the true result.
- Re-run.
.github/workflows/ci.yml
- id: lint
continue-on-error: true
run: npm run lint
- if: steps.lint.outcome == 'failure'
run: echo "lint failed but did not block the job"How to prevent it
- Use steps.<id>.outcome, not conclusion, after a continue-on-error step.
- Reserve continue-on-error for steps whose failure should not block the job.
Frequently asked questions
What causes ""continue-on-error did not propagate outcome""?
continue-on-error sets conclusion to success while leaving outcome as failure; conditions must read outcome to detect the real result.
How do I fix "continue-on-error did not propagate outcome"?
Gate on steps.<id>.outcome
Related guides
GitHub Actions needs context outputs are undefinedFix the GitHub Actions error where a downstream job reads needs.<job>.outputs.<name> and gets undefined becau…
GitHub Actions contains() returns unexpected results from a type mismatch in an ifFix an if condition where contains() compares mismatched types (number vs string, array vs scalar) and evalua…
GitHub Actions continue-on-error on a matrix hides a real failing legFix a matrix job that reports success because continue-on-error swallowed a genuinely failed combination.