Recover a Failed Make Scenario From an Incomplete Execution
When an external service fails after part of a scenario has succeeded, inspect that run before sending the whole event again. Use incomplete executions where the scenario and its error behavior support them.
Worked example
Order export recovery check
Fixture = Order E-22 First action = Upsert order row by E-22 Failed action = Upload packing file because test connection is unavailable After recovery = One row for E-22 and one packing file
Steps
- Enable storage of incomplete executions in the scenario settings and review the configured handling for the failure you want to recover.
- In a test run, make a downstream operation fail after the source fixture has already been read or written. Inspect the run detail and the incomplete execution.
- Correct the underlying dependency, then resume or retry the saved run as appropriate. Check which module runs next and verify the destination result.
- Use the event ID to detect any earlier write. For a write that may have succeeded before the connection broke, check the destination record before repeating it.
What to check
- Verify that the failure creates a stored execution under your actual settings. Behavior depends on the exception and the chosen handler.
- Check whether automatic retries are active before manually resuming the same run.