## TL;DR

Consequence jobs (skipped or canceled because upstream failed) need no fix. Sort each failing job into four buckets using its failure_reason.

## Fix

1. Consequence jobs (skipped or canceled because upstream failed) need no fix.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this GitLab CI feature.
- The symptom matches: triage failing jobs by failure_reason before touching code.

## When NOT to use

- Unrelated GitLab CI issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against GitLab CI. Source: https://github.com/p3bot/library/blob/HEAD/tasks/gitlab/pipeline/review/task.md.

## Variant phrasings

### triage failing jobs by failure_reason before touching code

## Why it happens

A GitLab pipeline fails and you need to decide whether the failure is yours, infra, or an external verdict.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/p3bot/library/blob/HEAD/tasks/gitlab/pipeline/review/task.md