Repair AWS Step Functions Retry Budget Explosion

Repair AWS Step Functions Retry Budget Explosion — EVIDENCE-LIMITED REVIEW

Scenario received

A transient failure causes a workflow to repeat a billable downstream job many times.

Evidence inventory

• S1: state machine definitions — partial extract described by the requester; original full source not provided here.
• S2: execution histories — partial extract described by the requester; original full source not provided here.
• S3: retry backoff settings — NOT PROVIDED; required to validate dependent findings.
• S4: downstream idempotency logs — NOT PROVIDED; required to validate dependent findings.

Case-specific checks

Map Retry and Catch branch behavior. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
2.

Count total attempt budget. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
3.

Identify side effect replay paths. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
4.

Test terminal and transient faults. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.

Deliverables

Retry amplification graph. Create an evidence-linked section with observations, missing data, owner and next validation step.

State machine correction. Create an evidence-linked section with observations, missing data, owner and next validation step.

Bounded fault test cases. Create an evidence-linked section with observations, missing data, owner and next validation step.

Acceptance gate

The proposed retry budget protects idempotency and clarifies when operator intervention is required. Do not label this gate passed until supplied source records actually demonstrate it.

Verdict and next action

INCOMPLETE — evidence required. Request S3 and S4 from the authorized owner, reconcile them with S1 and S2, then repeat the four checks and log remaining conflicts. No production change, approval, communication, or test run is claimed.