FAILURE MAP
← Case archive

FA-6662 / HTTP retries / Member archive

Status retries require both a configured status and a replayable body · case 02

Status retries require both a configured status and a replayable body.

Member previewVariant 2 · 3 implementations · 4 checks per implementation

Case contract

Status retries require both a configured status and a replayable body: return the result specified by the explicit input/output boundary fixtures.

Why this case matters

This deterministic http retries model isolates the retry-response policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
fixture 1truefalseFailed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗