GitHub Actions if: always() still skipped when dependency is canceled

By Daniel Zoghalchali·Latchkey

always() forces a step to run regardless of prior success or failure, but a canceled run can still stop dependent jobs. Understanding always() vs !cancelled() prevents surprising skips.

What this error means

A cleanup step with if: always() does not run after the workflow is canceled, or a dependent job is skipped on cancellation despite always().

# Cleanup did not run because the job was canceled upstream
- if: always()
  run: ./cleanup.sh

Common causes

Cancellation propagates as a skip

A canceled dependency can skip downstream jobs even with always() at step scope.

Confusing always() with !cancelled()

always() runs on failure but you may actually want to honor cancellation differently.

How to fix it

Choose the correct status function

1. Use if: always() to run on success, failure, and cancellation at the step level.
2. Use if: \${{ !cancelled() }} to run unless canceled.
3. For dependent jobs, combine status functions with needs.<job>.result checks.

- name: Always upload logs
  if: always()
  uses: actions/upload-artifact@v4
  with:
    name: logs
    path: ./logs

How to prevent it

• Pick always() vs !cancelled() vs success()/failure() deliberately.
• Test cancellation paths, not just success, for cleanup steps.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions