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-1101

Start a durable workflow execution: A duplicate start creates a second active execution · case 01

The workflow start operation is admitted even though a duplicate start creates a second active execution.

Workflow orchestration● Open access↗
FA-1102

Start a durable workflow execution: A duplicate start creates a second active execution · case 02

The workflow start operation is admitted even though a duplicate start creates a second active execution.

Workflow orchestration◈ Members↗
FA-1103

Start a durable workflow execution: A duplicate start creates a second active execution · case 03

The workflow start operation is admitted even though a duplicate start creates a second active execution.

Workflow orchestration◈ Members↗
FA-1104

Start a durable workflow execution: A duplicate start creates a second active execution · case 04

The workflow start operation is admitted even though a duplicate start creates a second active execution.

Workflow orchestration◈ Members↗
FA-1105

Start a durable workflow execution: A duplicate start creates a second active execution · case 05

The workflow start operation is admitted even though a duplicate start creates a second active execution.

Workflow orchestration◈ Members↗
FA-1106

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 01

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Workflow orchestration● Open access↗
FA-1107

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 02

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Workflow orchestration◈ Members↗
FA-1108

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 03

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Workflow orchestration◈ Members↗
FA-1109

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 04

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Workflow orchestration◈ Members↗
FA-1110

Start a durable workflow execution: The workflow starts on an unavailable definition version · case 05

The workflow start operation is admitted even though the workflow starts on an unavailable definition version.

Workflow orchestration◈ Members↗
FA-1111

Start a durable workflow execution: A workflow starts without its required input fields · case 01

The workflow start operation is admitted even though a workflow starts without its required input fields.

Workflow orchestration● Open access↗
FA-1112

Start a durable workflow execution: A workflow starts without its required input fields · case 02

The workflow start operation is admitted even though a workflow starts without its required input fields.

Workflow orchestration◈ Members↗
FA-1113

Start a durable workflow execution: A workflow starts without its required input fields · case 03

The workflow start operation is admitted even though a workflow starts without its required input fields.

Workflow orchestration◈ Members↗
FA-1114

Start a durable workflow execution: A workflow starts without its required input fields · case 04

The workflow start operation is admitted even though a workflow starts without its required input fields.

Workflow orchestration◈ Members↗
FA-1115

Start a durable workflow execution: A workflow starts without its required input fields · case 05

The workflow start operation is admitted even though a workflow starts without its required input fields.

Workflow orchestration◈ Members↗
FA-1116

Start a durable workflow execution: A child starts after its parent was cancelled · case 01

The workflow start operation is admitted even though a child starts after its parent was cancelled.

Workflow orchestration● Open access↗
FA-1117

Start a durable workflow execution: A child starts after its parent was cancelled · case 02

The workflow start operation is admitted even though a child starts after its parent was cancelled.

Workflow orchestration◈ Members↗
FA-1118

Start a durable workflow execution: A child starts after its parent was cancelled · case 03

The workflow start operation is admitted even though a child starts after its parent was cancelled.

Workflow orchestration◈ Members↗
FA-1119

Start a durable workflow execution: A child starts after its parent was cancelled · case 04

The workflow start operation is admitted even though a child starts after its parent was cancelled.

Workflow orchestration◈ Members↗
FA-1120

Start a durable workflow execution: A child starts after its parent was cancelled · case 05

The workflow start operation is admitted even though a child starts after its parent was cancelled.

Workflow orchestration◈ Members↗
FA-1121

Start a durable workflow execution: A deferred start begins beyond the workflow start deadline · case 01

The workflow start operation is admitted even though a deferred start begins beyond the workflow start deadline.

Workflow orchestration● Open access↗
FA-1122

Start a durable workflow execution: A deferred start begins beyond the workflow start deadline · case 02

The workflow start operation is admitted even though a deferred start begins beyond the workflow start deadline.

Workflow orchestration◈ Members↗
FA-1123

Start a durable workflow execution: A deferred start begins beyond the workflow start deadline · case 03

The workflow start operation is admitted even though a deferred start begins beyond the workflow start deadline.

Workflow orchestration◈ Members↗
FA-1124

Start a durable workflow execution: A deferred start begins beyond the workflow start deadline · case 04

The workflow start operation is admitted even though a deferred start begins beyond the workflow start deadline.

Workflow orchestration◈ Members↗
FA-1125

Start a durable workflow execution: A deferred start begins beyond the workflow start deadline · case 05

The workflow start operation is admitted even though a deferred start begins beyond the workflow start deadline.

Workflow orchestration◈ Members↗
FA-1126

Accept a durable activity completion: A completion from a previous workflow run is accepted · case 01

The activity completion operation is admitted even though a completion from a previous workflow run is accepted.

Workflow orchestration● Open access↗
FA-1127

Accept a durable activity completion: A completion from a previous workflow run is accepted · case 02

The activity completion operation is admitted even though a completion from a previous workflow run is accepted.

Workflow orchestration◈ Members↗
FA-1128

Accept a durable activity completion: A completion from a previous workflow run is accepted · case 03

The activity completion operation is admitted even though a completion from a previous workflow run is accepted.

Workflow orchestration◈ Members↗
FA-1129

Accept a durable activity completion: A completion from a previous workflow run is accepted · case 04

The activity completion operation is admitted even though a completion from a previous workflow run is accepted.

Workflow orchestration◈ Members↗
FA-1130

Accept a durable activity completion: A completion from a previous workflow run is accepted · case 05

The activity completion operation is admitted even though a completion from a previous workflow run is accepted.

Workflow orchestration◈ Members↗
FA-1131

Accept a durable activity completion: A timed-out activity attempt overwrites its successor · case 01

The activity completion operation is admitted even though a timed-out activity attempt overwrites its successor.

Workflow orchestration● Open access↗
FA-1132

Accept a durable activity completion: A timed-out activity attempt overwrites its successor · case 02

The activity completion operation is admitted even though a timed-out activity attempt overwrites its successor.

Workflow orchestration◈ Members↗
FA-1133

Accept a durable activity completion: A timed-out activity attempt overwrites its successor · case 03

The activity completion operation is admitted even though a timed-out activity attempt overwrites its successor.

Workflow orchestration◈ Members↗
FA-1134

Accept a durable activity completion: A timed-out activity attempt overwrites its successor · case 04

The activity completion operation is admitted even though a timed-out activity attempt overwrites its successor.

Workflow orchestration◈ Members↗
FA-1135

Accept a durable activity completion: A timed-out activity attempt overwrites its successor · case 05

The activity completion operation is admitted even though a timed-out activity attempt overwrites its successor.

Workflow orchestration◈ Members↗
FA-1136

Accept a durable activity completion: An unsolicited completion invents an unscheduled activity · case 01

The activity completion operation is admitted even though an unsolicited completion invents an unscheduled activity.

Workflow orchestration● Open access↗
FA-1137

Accept a durable activity completion: An unsolicited completion invents an unscheduled activity · case 02

The activity completion operation is admitted even though an unsolicited completion invents an unscheduled activity.

Workflow orchestration◈ Members↗
FA-1138

Accept a durable activity completion: An unsolicited completion invents an unscheduled activity · case 03

The activity completion operation is admitted even though an unsolicited completion invents an unscheduled activity.

Workflow orchestration◈ Members↗
FA-1139

Accept a durable activity completion: An unsolicited completion invents an unscheduled activity · case 04

The activity completion operation is admitted even though an unsolicited completion invents an unscheduled activity.

Workflow orchestration◈ Members↗
FA-1140

Accept a durable activity completion: An unsolicited completion invents an unscheduled activity · case 05

The activity completion operation is admitted even though an unsolicited completion invents an unscheduled activity.

Workflow orchestration◈ Members↗
FA-1141

Accept a durable activity completion: An incompatible activity result enters durable history · case 01

The activity completion operation is admitted even though an incompatible activity result enters durable history.

Workflow orchestration● Open access↗
FA-1142

Accept a durable activity completion: An incompatible activity result enters durable history · case 02

The activity completion operation is admitted even though an incompatible activity result enters durable history.

Workflow orchestration◈ Members↗
FA-1143

Accept a durable activity completion: An incompatible activity result enters durable history · case 03

The activity completion operation is admitted even though an incompatible activity result enters durable history.

Workflow orchestration◈ Members↗
FA-1144

Accept a durable activity completion: An incompatible activity result enters durable history · case 04

The activity completion operation is admitted even though an incompatible activity result enters durable history.

Workflow orchestration◈ Members↗
FA-1145

Accept a durable activity completion: An incompatible activity result enters durable history · case 05

The activity completion operation is admitted even though an incompatible activity result enters durable history.

Workflow orchestration◈ Members↗
FA-1146

Accept a durable activity completion: A duplicate activity completion schedules downstream work twice · case 01

The activity completion operation is admitted even though a duplicate activity completion schedules downstream work twice.

Workflow orchestration● Open access↗
FA-1147

Accept a durable activity completion: A duplicate activity completion schedules downstream work twice · case 02

The activity completion operation is admitted even though a duplicate activity completion schedules downstream work twice.

Workflow orchestration◈ Members↗
FA-1148

Accept a durable activity completion: A duplicate activity completion schedules downstream work twice · case 03

The activity completion operation is admitted even though a duplicate activity completion schedules downstream work twice.

Workflow orchestration◈ Members↗
FA-1149

Accept a durable activity completion: A duplicate activity completion schedules downstream work twice · case 04

The activity completion operation is admitted even though a duplicate activity completion schedules downstream work twice.

Workflow orchestration◈ Members↗
FA-1150

Accept a durable activity completion: A duplicate activity completion schedules downstream work twice · case 05

The activity completion operation is admitted even though a duplicate activity completion schedules downstream work twice.

Workflow orchestration◈ Members↗
FA-1151

Fire a durable workflow timer: A timer fires before its scheduled timestamp · case 01

The workflow timer operation is admitted even though a timer fires before its scheduled timestamp.

Workflow orchestration● Open access↗
FA-1152

Fire a durable workflow timer: A timer fires before its scheduled timestamp · case 02

The workflow timer operation is admitted even though a timer fires before its scheduled timestamp.

Workflow orchestration◈ Members↗
FA-1153

Fire a durable workflow timer: A timer fires before its scheduled timestamp · case 03

The workflow timer operation is admitted even though a timer fires before its scheduled timestamp.

Workflow orchestration◈ Members↗
FA-1154

Fire a durable workflow timer: A timer fires before its scheduled timestamp · case 04

The workflow timer operation is admitted even though a timer fires before its scheduled timestamp.

Workflow orchestration◈ Members↗
FA-1155

Fire a durable workflow timer: A timer fires before its scheduled timestamp · case 05

The workflow timer operation is admitted even though a timer fires before its scheduled timestamp.

Workflow orchestration◈ Members↗
FA-1156

Fire a durable workflow timer: A cancelled timer resumes workflow execution · case 01

The workflow timer operation is admitted even though a cancelled timer resumes workflow execution.

Workflow orchestration● Open access↗
FA-1157

Fire a durable workflow timer: A cancelled timer resumes workflow execution · case 02

The workflow timer operation is admitted even though a cancelled timer resumes workflow execution.

Workflow orchestration◈ Members↗
FA-1158

Fire a durable workflow timer: A cancelled timer resumes workflow execution · case 03

The workflow timer operation is admitted even though a cancelled timer resumes workflow execution.

Workflow orchestration◈ Members↗
FA-1159

Fire a durable workflow timer: A cancelled timer resumes workflow execution · case 04

The workflow timer operation is admitted even though a cancelled timer resumes workflow execution.

Workflow orchestration◈ Members↗
FA-1160

Fire a durable workflow timer: A cancelled timer resumes workflow execution · case 05

The workflow timer operation is admitted even though a cancelled timer resumes workflow execution.

Workflow orchestration◈ Members↗
FA-1161

Fire a durable workflow timer: A stale timer wakeup fires a replacement timer · case 01

The workflow timer operation is admitted even though a stale timer wakeup fires a replacement timer.

Workflow orchestration● Open access↗
FA-1162

Fire a durable workflow timer: A stale timer wakeup fires a replacement timer · case 02

The workflow timer operation is admitted even though a stale timer wakeup fires a replacement timer.

Workflow orchestration◈ Members↗
FA-1163

Fire a durable workflow timer: A stale timer wakeup fires a replacement timer · case 03

The workflow timer operation is admitted even though a stale timer wakeup fires a replacement timer.

Workflow orchestration◈ Members↗
FA-1164

Fire a durable workflow timer: A stale timer wakeup fires a replacement timer · case 04

The workflow timer operation is admitted even though a stale timer wakeup fires a replacement timer.

Workflow orchestration◈ Members↗
FA-1165

Fire a durable workflow timer: A stale timer wakeup fires a replacement timer · case 05

The workflow timer operation is admitted even though a stale timer wakeup fires a replacement timer.

Workflow orchestration◈ Members↗
FA-1166

Fire a durable workflow timer: A timer reactivates a completed workflow · case 01

The workflow timer operation is admitted even though a timer reactivates a completed workflow.

Workflow orchestration● Open access↗
FA-1167

Fire a durable workflow timer: A timer reactivates a completed workflow · case 02

The workflow timer operation is admitted even though a timer reactivates a completed workflow.

Workflow orchestration◈ Members↗
FA-1168

Fire a durable workflow timer: A timer reactivates a completed workflow · case 03

The workflow timer operation is admitted even though a timer reactivates a completed workflow.

Workflow orchestration◈ Members↗
FA-1169

Fire a durable workflow timer: A timer reactivates a completed workflow · case 04

The workflow timer operation is admitted even though a timer reactivates a completed workflow.

Workflow orchestration◈ Members↗
FA-1170

Fire a durable workflow timer: A timer reactivates a completed workflow · case 05

The workflow timer operation is admitted even though a timer reactivates a completed workflow.

Workflow orchestration◈ Members↗
FA-1171

Fire a durable workflow timer: A retried timer delivery produces another history event · case 01

The workflow timer operation is admitted even though a retried timer delivery produces another history event.

Workflow orchestration● Open access↗
FA-1172

Fire a durable workflow timer: A retried timer delivery produces another history event · case 02

The workflow timer operation is admitted even though a retried timer delivery produces another history event.

Workflow orchestration◈ Members↗
FA-1173

Fire a durable workflow timer: A retried timer delivery produces another history event · case 03

The workflow timer operation is admitted even though a retried timer delivery produces another history event.

Workflow orchestration◈ Members↗
FA-1174

Fire a durable workflow timer: A retried timer delivery produces another history event · case 04

The workflow timer operation is admitted even though a retried timer delivery produces another history event.

Workflow orchestration◈ Members↗
FA-1175

Fire a durable workflow timer: A retried timer delivery produces another history event · case 05

The workflow timer operation is admitted even though a retried timer delivery produces another history event.

Workflow orchestration◈ Members↗
FA-1176

Deliver a signal to a durable workflow: Duplicate signal delivery applies the external command twice · case 01

The workflow signal operation is admitted even though duplicate signal delivery applies the external command twice.

Workflow orchestration● Open access↗
FA-1177

Deliver a signal to a durable workflow: Duplicate signal delivery applies the external command twice · case 02

The workflow signal operation is admitted even though duplicate signal delivery applies the external command twice.

Workflow orchestration◈ Members↗
FA-1178

Deliver a signal to a durable workflow: Duplicate signal delivery applies the external command twice · case 03

The workflow signal operation is admitted even though duplicate signal delivery applies the external command twice.

Workflow orchestration◈ Members↗
FA-1179

Deliver a signal to a durable workflow: Duplicate signal delivery applies the external command twice · case 04

The workflow signal operation is admitted even though duplicate signal delivery applies the external command twice.

Workflow orchestration◈ Members↗
FA-1180

Deliver a signal to a durable workflow: Duplicate signal delivery applies the external command twice · case 05

The workflow signal operation is admitted even though duplicate signal delivery applies the external command twice.

Workflow orchestration◈ Members↗
FA-1181

Deliver a signal to a durable workflow: A delayed signal reaches a different run under the same workflow name · case 01

The workflow signal operation is admitted even though a delayed signal reaches a different run under the same workflow name.

Workflow orchestration● Open access↗
FA-1182

Deliver a signal to a durable workflow: A delayed signal reaches a different run under the same workflow name · case 02

The workflow signal operation is admitted even though a delayed signal reaches a different run under the same workflow name.

Workflow orchestration◈ Members↗
FA-1183

Deliver a signal to a durable workflow: A delayed signal reaches a different run under the same workflow name · case 03

The workflow signal operation is admitted even though a delayed signal reaches a different run under the same workflow name.

Workflow orchestration◈ Members↗
FA-1184

Deliver a signal to a durable workflow: A delayed signal reaches a different run under the same workflow name · case 04

The workflow signal operation is admitted even though a delayed signal reaches a different run under the same workflow name.

Workflow orchestration◈ Members↗
FA-1185

Deliver a signal to a durable workflow: A delayed signal reaches a different run under the same workflow name · case 05

The workflow signal operation is admitted even though a delayed signal reaches a different run under the same workflow name.

Workflow orchestration◈ Members↗
FA-1186

Deliver a signal to a durable workflow: An unknown signal type bypasses workflow dispatch · case 01

The workflow signal operation is admitted even though an unknown signal type bypasses workflow dispatch.

Workflow orchestration● Open access↗
FA-1187

Deliver a signal to a durable workflow: An unknown signal type bypasses workflow dispatch · case 02

The workflow signal operation is admitted even though an unknown signal type bypasses workflow dispatch.

Workflow orchestration◈ Members↗
FA-1188

Deliver a signal to a durable workflow: An unknown signal type bypasses workflow dispatch · case 03

The workflow signal operation is admitted even though an unknown signal type bypasses workflow dispatch.

Workflow orchestration◈ Members↗
FA-1189

Deliver a signal to a durable workflow: An unknown signal type bypasses workflow dispatch · case 04

The workflow signal operation is admitted even though an unknown signal type bypasses workflow dispatch.

Workflow orchestration◈ Members↗
FA-1190

Deliver a signal to a durable workflow: An unknown signal type bypasses workflow dispatch · case 05

The workflow signal operation is admitted even though an unknown signal type bypasses workflow dispatch.

Workflow orchestration◈ Members↗
FA-1191

Deliver a signal to a durable workflow: External signals exhaust the workflow pending-event budget · case 01

The workflow signal operation is admitted even though external signals exhaust the workflow pending-event budget.

Workflow orchestration● Open access↗
FA-1192

Deliver a signal to a durable workflow: External signals exhaust the workflow pending-event budget · case 02

The workflow signal operation is admitted even though external signals exhaust the workflow pending-event budget.

Workflow orchestration◈ Members↗
FA-1193

Deliver a signal to a durable workflow: External signals exhaust the workflow pending-event budget · case 03

The workflow signal operation is admitted even though external signals exhaust the workflow pending-event budget.

Workflow orchestration◈ Members↗
FA-1194

Deliver a signal to a durable workflow: External signals exhaust the workflow pending-event budget · case 04

The workflow signal operation is admitted even though external signals exhaust the workflow pending-event budget.

Workflow orchestration◈ Members↗
FA-1195

Deliver a signal to a durable workflow: External signals exhaust the workflow pending-event budget · case 05

The workflow signal operation is admitted even though external signals exhaust the workflow pending-event budget.

Workflow orchestration◈ Members↗
FA-1196

Deliver a signal to a durable workflow: A signal is applied before its required earlier command · case 01

The workflow signal operation is admitted even though a signal is applied before its required earlier command.

Workflow orchestration● Open access↗
FA-1197

Deliver a signal to a durable workflow: A signal is applied before its required earlier command · case 02

The workflow signal operation is admitted even though a signal is applied before its required earlier command.

Workflow orchestration◈ Members↗
FA-1198

Deliver a signal to a durable workflow: A signal is applied before its required earlier command · case 03

The workflow signal operation is admitted even though a signal is applied before its required earlier command.

Workflow orchestration◈ Members↗
FA-1199

Deliver a signal to a durable workflow: A signal is applied before its required earlier command · case 04

The workflow signal operation is admitted even though a signal is applied before its required earlier command.

Workflow orchestration◈ Members↗
FA-1200

Deliver a signal to a durable workflow: A signal is applied before its required earlier command · case 05

The workflow signal operation is admitted even though a signal is applied before its required earlier command.

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 ↗