## TL;DR

Per StackHawk failure semantics: treat 42 as a finding to triage and 1 as a config error to fix - retrying 42 is always wrong.

## Steps

1. Per StackHawk failure semantics: treat 42 as a finding to triage and 1 as a config error to fix - retrying 42 is always wrong.

## When to use

You are seeing this: Exit 0: scan ran, nothing at or above failureThreshold - pass. Use this skill when you run into "HawkScan exit code 42 means findings, not failure - never retry it like a flake".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
