FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-1201

Run a saga compensation action: Compensation reverses a forward action that never committed · case 01

The saga compensation operation is admitted even though compensation reverses a forward action that never committed.

Workflow orchestration● Open access↗
FA-1202

Run a saga compensation action: Compensation reverses a forward action that never committed · case 02

The saga compensation operation is admitted even though compensation reverses a forward action that never committed.

Workflow orchestration◈ Members↗
FA-1203

Run a saga compensation action: Compensation reverses a forward action that never committed · case 03

The saga compensation operation is admitted even though compensation reverses a forward action that never committed.

Workflow orchestration◈ Members↗
FA-1204

Run a saga compensation action: Compensation reverses a forward action that never committed · case 04

The saga compensation operation is admitted even though compensation reverses a forward action that never committed.

Workflow orchestration◈ Members↗
FA-1205

Run a saga compensation action: Compensation reverses a forward action that never committed · case 05

The saga compensation operation is admitted even though compensation reverses a forward action that never committed.

Workflow orchestration◈ Members↗
FA-1206

Run a saga compensation action: An upstream step is compensated while dependents remain active · case 01

The saga compensation operation is admitted even though an upstream step is compensated while dependents remain active.

Workflow orchestration● Open access↗
FA-1207

Run a saga compensation action: An upstream step is compensated while dependents remain active · case 02

The saga compensation operation is admitted even though an upstream step is compensated while dependents remain active.

Workflow orchestration◈ Members↗
FA-1208

Run a saga compensation action: An upstream step is compensated while dependents remain active · case 03

The saga compensation operation is admitted even though an upstream step is compensated while dependents remain active.

Workflow orchestration◈ Members↗
FA-1209

Run a saga compensation action: An upstream step is compensated while dependents remain active · case 04

The saga compensation operation is admitted even though an upstream step is compensated while dependents remain active.

Workflow orchestration◈ Members↗
FA-1210

Run a saga compensation action: An upstream step is compensated while dependents remain active · case 05

The saga compensation operation is admitted even though an upstream step is compensated while dependents remain active.

Workflow orchestration◈ Members↗
FA-1211

Run a saga compensation action: Retried compensation refunds the same side effect twice · case 01

The saga compensation operation is admitted even though retried compensation refunds the same side effect twice.

Workflow orchestration● Open access↗
FA-1212

Run a saga compensation action: Retried compensation refunds the same side effect twice · case 02

The saga compensation operation is admitted even though retried compensation refunds the same side effect twice.

Workflow orchestration◈ Members↗
FA-1213

Run a saga compensation action: Retried compensation refunds the same side effect twice · case 03

The saga compensation operation is admitted even though retried compensation refunds the same side effect twice.

Workflow orchestration◈ Members↗
FA-1214

Run a saga compensation action: Retried compensation refunds the same side effect twice · case 04

The saga compensation operation is admitted even though retried compensation refunds the same side effect twice.

Workflow orchestration◈ Members↗
FA-1215

Run a saga compensation action: Retried compensation refunds the same side effect twice · case 05

The saga compensation operation is admitted even though retried compensation refunds the same side effect twice.

Workflow orchestration◈ Members↗
FA-1216

Run a saga compensation action: Compensation overwrites a resource changed by another workflow · case 01

The saga compensation operation is admitted even though compensation overwrites a resource changed by another workflow.

Workflow orchestration● Open access↗
FA-1217

Run a saga compensation action: Compensation overwrites a resource changed by another workflow · case 02

The saga compensation operation is admitted even though compensation overwrites a resource changed by another workflow.

Workflow orchestration◈ Members↗
FA-1218

Run a saga compensation action: Compensation overwrites a resource changed by another workflow · case 03

The saga compensation operation is admitted even though compensation overwrites a resource changed by another workflow.

Workflow orchestration◈ Members↗
FA-1219

Run a saga compensation action: Compensation overwrites a resource changed by another workflow · case 04

The saga compensation operation is admitted even though compensation overwrites a resource changed by another workflow.

Workflow orchestration◈ Members↗
FA-1220

Run a saga compensation action: Compensation overwrites a resource changed by another workflow · case 05

The saga compensation operation is admitted even though compensation overwrites a resource changed by another workflow.

Workflow orchestration◈ Members↗
FA-1221

Run a saga compensation action: A committed step has no recorded inverse operation · case 01

The saga compensation operation is admitted even though a committed step has no recorded inverse operation.

Workflow orchestration● Open access↗
FA-1222

Run a saga compensation action: A committed step has no recorded inverse operation · case 02

The saga compensation operation is admitted even though a committed step has no recorded inverse operation.

Workflow orchestration◈ Members↗
FA-1223

Run a saga compensation action: A committed step has no recorded inverse operation · case 03

The saga compensation operation is admitted even though a committed step has no recorded inverse operation.

Workflow orchestration◈ Members↗
FA-1224

Run a saga compensation action: A committed step has no recorded inverse operation · case 04

The saga compensation operation is admitted even though a committed step has no recorded inverse operation.

Workflow orchestration◈ Members↗
FA-1225

Run a saga compensation action: A committed step has no recorded inverse operation · case 05

The saga compensation operation is admitted even though a committed step has no recorded inverse operation.

Workflow orchestration◈ Members↗
FA-1226

Replay durable workflow history: Replayed code emits a different command kind than history · case 01

The workflow replay operation is admitted even though replayed code emits a different command kind than history.

Workflow orchestration● Open access↗
FA-1227

Replay durable workflow history: Replayed code emits a different command kind than history · case 02

The workflow replay operation is admitted even though replayed code emits a different command kind than history.

Workflow orchestration◈ Members↗
FA-1228

Replay durable workflow history: Replayed code emits a different command kind than history · case 03

The workflow replay operation is admitted even though replayed code emits a different command kind than history.

Workflow orchestration◈ Members↗
FA-1229

Replay durable workflow history: Replayed code emits a different command kind than history · case 04

The workflow replay operation is admitted even though replayed code emits a different command kind than history.

Workflow orchestration◈ Members↗
FA-1230

Replay durable workflow history: Replayed code emits a different command kind than history · case 05

The workflow replay operation is admitted even though replayed code emits a different command kind than history.

Workflow orchestration◈ Members↗
FA-1231

Replay durable workflow history: Replayed commands reverse the recorded causal order · case 01

The workflow replay operation is admitted even though replayed commands reverse the recorded causal order.

Workflow orchestration● Open access↗
FA-1232

Replay durable workflow history: Replayed commands reverse the recorded causal order · case 02

The workflow replay operation is admitted even though replayed commands reverse the recorded causal order.

Workflow orchestration◈ Members↗
FA-1233

Replay durable workflow history: Replayed commands reverse the recorded causal order · case 03

The workflow replay operation is admitted even though replayed commands reverse the recorded causal order.

Workflow orchestration◈ Members↗
FA-1234

Replay durable workflow history: Replayed commands reverse the recorded causal order · case 04

The workflow replay operation is admitted even though replayed commands reverse the recorded causal order.

Workflow orchestration◈ Members↗
FA-1235

Replay durable workflow history: Replayed commands reverse the recorded causal order · case 05

The workflow replay operation is admitted even though replayed commands reverse the recorded causal order.

Workflow orchestration◈ Members↗
FA-1236

Replay durable workflow history: Code executes a branch not selected by the recorded marker · case 01

The workflow replay operation is admitted even though code executes a branch not selected by the recorded marker.

Workflow orchestration● Open access↗
FA-1237

Replay durable workflow history: Code executes a branch not selected by the recorded marker · case 02

The workflow replay operation is admitted even though code executes a branch not selected by the recorded marker.

Workflow orchestration◈ Members↗
FA-1238

Replay durable workflow history: Code executes a branch not selected by the recorded marker · case 03

The workflow replay operation is admitted even though code executes a branch not selected by the recorded marker.

Workflow orchestration◈ Members↗
FA-1239

Replay durable workflow history: Code executes a branch not selected by the recorded marker · case 04

The workflow replay operation is admitted even though code executes a branch not selected by the recorded marker.

Workflow orchestration◈ Members↗
FA-1240

Replay durable workflow history: Code executes a branch not selected by the recorded marker · case 05

The workflow replay operation is admitted even though code executes a branch not selected by the recorded marker.

Workflow orchestration◈ Members↗
FA-1241

Replay durable workflow history: Replay consumes an unrecorded nondeterministic random value · case 01

The workflow replay operation is admitted even though replay consumes an unrecorded nondeterministic random value.

Workflow orchestration● Open access↗
FA-1242

Replay durable workflow history: Replay consumes an unrecorded nondeterministic random value · case 02

The workflow replay operation is admitted even though replay consumes an unrecorded nondeterministic random value.

Workflow orchestration◈ Members↗
FA-1243

Replay durable workflow history: Replay consumes an unrecorded nondeterministic random value · case 03

The workflow replay operation is admitted even though replay consumes an unrecorded nondeterministic random value.

Workflow orchestration◈ Members↗
FA-1244

Replay durable workflow history: Replay consumes an unrecorded nondeterministic random value · case 04

The workflow replay operation is admitted even though replay consumes an unrecorded nondeterministic random value.

Workflow orchestration◈ Members↗
FA-1245

Replay durable workflow history: Replay consumes an unrecorded nondeterministic random value · case 05

The workflow replay operation is admitted even though replay consumes an unrecorded nondeterministic random value.

Workflow orchestration◈ Members↗
FA-1246

Replay durable workflow history: Replay silently skips a missing history event · case 01

The workflow replay operation is admitted even though replay silently skips a missing history event.

Workflow orchestration● Open access↗
FA-1247

Replay durable workflow history: Replay silently skips a missing history event · case 02

The workflow replay operation is admitted even though replay silently skips a missing history event.

Workflow orchestration◈ Members↗
FA-1248

Replay durable workflow history: Replay silently skips a missing history event · case 03

The workflow replay operation is admitted even though replay silently skips a missing history event.

Workflow orchestration◈ Members↗
FA-1249

Replay durable workflow history: Replay silently skips a missing history event · case 04

The workflow replay operation is admitted even though replay silently skips a missing history event.

Workflow orchestration◈ Members↗
FA-1250

Replay durable workflow history: Replay silently skips a missing history event · case 05

The workflow replay operation is admitted even though replay silently skips a missing history event.

Workflow orchestration◈ Members↗
FA-1251

Continue a workflow as a new run: Continuation loses unresolved activity results · case 01

The workflow continue operation is admitted even though continuation loses unresolved activity results.

Workflow orchestration● Open access↗
FA-1252

Continue a workflow as a new run: Continuation loses unresolved activity results · case 02

The workflow continue operation is admitted even though continuation loses unresolved activity results.

Workflow orchestration◈ Members↗
FA-1253

Continue a workflow as a new run: Continuation loses unresolved activity results · case 03

The workflow continue operation is admitted even though continuation loses unresolved activity results.

Workflow orchestration◈ Members↗
FA-1254

Continue a workflow as a new run: Continuation loses unresolved activity results · case 04

The workflow continue operation is admitted even though continuation loses unresolved activity results.

Workflow orchestration◈ Members↗
FA-1255

Continue a workflow as a new run: Continuation loses unresolved activity results · case 05

The workflow continue operation is admitted even though continuation loses unresolved activity results.

Workflow orchestration◈ Members↗
FA-1256

Continue a workflow as a new run: Continuation discards accepted but unconsumed signals · case 01

The workflow continue operation is admitted even though continuation discards accepted but unconsumed signals.

Workflow orchestration● Open access↗
FA-1257

Continue a workflow as a new run: Continuation discards accepted but unconsumed signals · case 02

The workflow continue operation is admitted even though continuation discards accepted but unconsumed signals.

Workflow orchestration◈ Members↗
FA-1258

Continue a workflow as a new run: Continuation discards accepted but unconsumed signals · case 03

The workflow continue operation is admitted even though continuation discards accepted but unconsumed signals.

Workflow orchestration◈ Members↗
FA-1259

Continue a workflow as a new run: Continuation discards accepted but unconsumed signals · case 04

The workflow continue operation is admitted even though continuation discards accepted but unconsumed signals.

Workflow orchestration◈ Members↗
FA-1260

Continue a workflow as a new run: Continuation discards accepted but unconsumed signals · case 05

The workflow continue operation is admitted even though continuation discards accepted but unconsumed signals.

Workflow orchestration◈ Members↗
FA-1261

Continue a workflow as a new run: Continuation stores a runtime handle instead of durable state · case 01

The workflow continue operation is admitted even though continuation stores a runtime handle instead of durable state.

Workflow orchestration● Open access↗
FA-1262

Continue a workflow as a new run: Continuation stores a runtime handle instead of durable state · case 02

The workflow continue operation is admitted even though continuation stores a runtime handle instead of durable state.

Workflow orchestration◈ Members↗
FA-1263

Continue a workflow as a new run: Continuation stores a runtime handle instead of durable state · case 03

The workflow continue operation is admitted even though continuation stores a runtime handle instead of durable state.

Workflow orchestration◈ Members↗
FA-1264

Continue a workflow as a new run: Continuation stores a runtime handle instead of durable state · case 04

The workflow continue operation is admitted even though continuation stores a runtime handle instead of durable state.

Workflow orchestration◈ Members↗
FA-1265

Continue a workflow as a new run: Continuation stores a runtime handle instead of durable state · case 05

The workflow continue operation is admitted even though continuation stores a runtime handle instead of durable state.

Workflow orchestration◈ Members↗
FA-1266

Continue a workflow as a new run: Continuation reuses the predecessor run identifier · case 01

The workflow continue operation is admitted even though continuation reuses the predecessor run identifier.

Workflow orchestration● Open access↗
FA-1267

Continue a workflow as a new run: Continuation reuses the predecessor run identifier · case 02

The workflow continue operation is admitted even though continuation reuses the predecessor run identifier.

Workflow orchestration◈ Members↗
FA-1268

Continue a workflow as a new run: Continuation reuses the predecessor run identifier · case 03

The workflow continue operation is admitted even though continuation reuses the predecessor run identifier.

Workflow orchestration◈ Members↗
FA-1269

Continue a workflow as a new run: Continuation reuses the predecessor run identifier · case 04

The workflow continue operation is admitted even though continuation reuses the predecessor run identifier.

Workflow orchestration◈ Members↗
FA-1270

Continue a workflow as a new run: Continuation reuses the predecessor run identifier · case 05

The workflow continue operation is admitted even though continuation reuses the predecessor run identifier.

Workflow orchestration◈ Members↗
FA-1271

Continue a workflow as a new run: Both predecessor and successor remain runnable · case 01

The workflow continue operation is admitted even though both predecessor and successor remain runnable.

Workflow orchestration● Open access↗
FA-1272

Continue a workflow as a new run: Both predecessor and successor remain runnable · case 02

The workflow continue operation is admitted even though both predecessor and successor remain runnable.

Workflow orchestration◈ Members↗
FA-1273

Continue a workflow as a new run: Both predecessor and successor remain runnable · case 03

The workflow continue operation is admitted even though both predecessor and successor remain runnable.

Workflow orchestration◈ Members↗
FA-1274

Continue a workflow as a new run: Both predecessor and successor remain runnable · case 04

The workflow continue operation is admitted even though both predecessor and successor remain runnable.

Workflow orchestration◈ Members↗
FA-1275

Continue a workflow as a new run: Both predecessor and successor remain runnable · case 05

The workflow continue operation is admitted even though both predecessor and successor remain runnable.

Workflow orchestration◈ Members↗
FA-1276

Complete workflow cancellation: Cancellation leaves dependent child workflows executing · case 01

The workflow cancel operation is admitted even though cancellation leaves dependent child workflows executing.

Workflow orchestration● Open access↗
FA-1277

Complete workflow cancellation: Cancellation leaves dependent child workflows executing · case 02

The workflow cancel operation is admitted even though cancellation leaves dependent child workflows executing.

Workflow orchestration◈ Members↗
FA-1278

Complete workflow cancellation: Cancellation leaves dependent child workflows executing · case 03

The workflow cancel operation is admitted even though cancellation leaves dependent child workflows executing.

Workflow orchestration◈ Members↗
FA-1279

Complete workflow cancellation: Cancellation leaves dependent child workflows executing · case 04

The workflow cancel operation is admitted even though cancellation leaves dependent child workflows executing.

Workflow orchestration◈ Members↗
FA-1280

Complete workflow cancellation: Cancellation leaves dependent child workflows executing · case 05

The workflow cancel operation is admitted even though cancellation leaves dependent child workflows executing.

Workflow orchestration◈ Members↗
FA-1281

Complete workflow cancellation: Cancellation completes before required activity cleanup · case 01

The workflow cancel operation is admitted even though cancellation completes before required activity cleanup.

Workflow orchestration● Open access↗
FA-1282

Complete workflow cancellation: Cancellation completes before required activity cleanup · case 02

The workflow cancel operation is admitted even though cancellation completes before required activity cleanup.

Workflow orchestration◈ Members↗
FA-1283

Complete workflow cancellation: Cancellation completes before required activity cleanup · case 03

The workflow cancel operation is admitted even though cancellation completes before required activity cleanup.

Workflow orchestration◈ Members↗
FA-1284

Complete workflow cancellation: Cancellation completes before required activity cleanup · case 04

The workflow cancel operation is admitted even though cancellation completes before required activity cleanup.

Workflow orchestration◈ Members↗
FA-1285

Complete workflow cancellation: Cancellation completes before required activity cleanup · case 05

The workflow cancel operation is admitted even though cancellation completes before required activity cleanup.

Workflow orchestration◈ Members↗
FA-1286

Complete workflow cancellation: Cancellation rewrites an already successful terminal result · case 01

The workflow cancel operation is admitted even though cancellation rewrites an already successful terminal result.

Workflow orchestration● Open access↗
FA-1287

Complete workflow cancellation: Cancellation rewrites an already successful terminal result · case 02

The workflow cancel operation is admitted even though cancellation rewrites an already successful terminal result.

Workflow orchestration◈ Members↗
FA-1288

Complete workflow cancellation: Cancellation rewrites an already successful terminal result · case 03

The workflow cancel operation is admitted even though cancellation rewrites an already successful terminal result.

Workflow orchestration◈ Members↗
FA-1289

Complete workflow cancellation: Cancellation rewrites an already successful terminal result · case 04

The workflow cancel operation is admitted even though cancellation rewrites an already successful terminal result.

Workflow orchestration◈ Members↗
FA-1290

Complete workflow cancellation: Cancellation rewrites an already successful terminal result · case 05

The workflow cancel operation is admitted even though cancellation rewrites an already successful terminal result.

Workflow orchestration◈ Members↗
FA-1291

Complete workflow cancellation: An old cancellation request terminates a newer run · case 01

The workflow cancel operation is admitted even though an old cancellation request terminates a newer run.

Workflow orchestration● Open access↗
FA-1292

Complete workflow cancellation: An old cancellation request terminates a newer run · case 02

The workflow cancel operation is admitted even though an old cancellation request terminates a newer run.

Workflow orchestration◈ Members↗
FA-1293

Complete workflow cancellation: An old cancellation request terminates a newer run · case 03

The workflow cancel operation is admitted even though an old cancellation request terminates a newer run.

Workflow orchestration◈ Members↗
FA-1294

Complete workflow cancellation: An old cancellation request terminates a newer run · case 04

The workflow cancel operation is admitted even though an old cancellation request terminates a newer run.

Workflow orchestration◈ Members↗
FA-1295

Complete workflow cancellation: An old cancellation request terminates a newer run · case 05

The workflow cancel operation is admitted even though an old cancellation request terminates a newer run.

Workflow orchestration◈ Members↗
FA-1296

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 01

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Workflow orchestration● Open access↗
FA-1297

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 02

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Workflow orchestration◈ Members↗
FA-1298

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 03

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Workflow orchestration◈ Members↗
FA-1299

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 04

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Workflow orchestration◈ Members↗
FA-1300

Complete workflow cancellation: Cancellation waits beyond its explicit cleanup deadline · case 05

The workflow cancel operation is admitted even though cancellation waits beyond its explicit cleanup deadline.

Workflow orchestration◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗