# Zapier recovery proof: targeted manual repair

Silent screen recording with descriptive captions; no speech or audio was recorded. The controlled test and source capture were made on 19 September 2026.

- 00:00:00.000 — Zapier's native Step 14 output shows manual recovery attempt 2 allowed for ROW-004. This was a live step test, not Replay or automatic recovery.
- 00:00:08.100 — At the saved failure checkpoint, 11 outcomes were accounted for. ROW-004 still showed Processing and Ready; the receiver remained pending.
- 00:00:18.167 — The final readback accounts for all 12 rows: six updates, two skips, four review outcomes and no failures. Only ROW-004 changed, to Shipped and Processed.
- 00:00:22.200 — This proves one targeted manual recovery. It does not prove automatic recovery, completion order or an exact task cost.

The clip is a retrospective with two hard cuts. The opening uses the approved source crop `x=130, y=300, w=980, h=1320` to isolate Zapier's Output Data and exclude the code, endpoint and private input fields. The crop is scaled to fit a 1920×1080 frame with side letterboxing. The two checkpoint scenes preserve the full source frame, scaled to fit with top and bottom letterboxing. The final frame is held for 2.5 seconds for reading.

The approved source ranges are `00:00.000–00:08.000`, `00:22.610–00:32.000` and `00:36.169–00:40.744`. Every other source range was excluded. The first scene shows `Gate Ok: true`, `Gate Status: allowed`, the batch `zapier-recovery-20260918-061145`, ROW-004 / ORDER-004 and write attempt `zapier-recovery-20260918-061145-ROW-004-attempt-2`.

The preserved failure checkpoint shows 11 accounted outcomes: five updates, two skips, four review outcomes and no reported failure. ROW-004 remained `Processing / Ready`, without the recovery batch ID; the receiver was pending and no completion event had been sent.

The final readback shows 12 accounted outcomes: six updates, two skips, four review outcomes and no failure. Only ROW-004 changed between the exact TSV snapshots, moving to `Shipped / Shipped / Processed` under the recovery batch. The final receiver record shows the batch complete with event `zapier-recovery-20260918-061145:complete` at `2026-09-19T12:42:32.929Z`.

Recovery used an edited Loop test record and individually tested live steps while the Zap remained off and unpublished. It was a targeted manual procedure, not automatic recovery, history Replay or a scheduled run. The approved clip does not show native root or child-run history, so it does not establish completion order. The readbacks prove saved cells, not the absence of repeated physical writes. Zapier did not expose an attributable recovery task total or independently metered failure-endpoint use in this package, so neither is claimed.

This proof covers one dated fictional fixture. It does not establish ongoing reliability, comparative ease, maintenance cost or future task pricing.