# Zapier backlog proof: scheduled run and zero-write replay

Silent screen recording with descriptive captions; no speech or audio was recorded. The source capture and the two selected runs are from 19 September 2026.

- 00:00:00.000 — We're checking the same 12 fictional orders in Zapier.
- 00:00:08.000 — Six should update. Four should stay held and two are already finished.
- 00:00:16.000 — On 19 September 2026, Zapier started run `01b57ba8-f452-ab39-cc3f-887185666ab4` from its schedule.
- 00:00:26.000 — Its batch ID is `80210f58-a647-42ae-8ddf-a31422044c96`.
- 00:00:35.000 — Zapier planned 6 updates, 4 holds, 2 skips and 10 input-row writes.
- 00:00:44.000 — Lovable now displays Zapier's saved baseline report.
- 00:00:51.000 — It shows 12 accounted rows, 4 exceptions and 0 failures.
- 00:00:59.000 — Zapier ran the schedule again as run `01b57ba8-7f9d-aa12-209e-60eff41e8524`.
- 00:01:09.000 — The replay batch ID is `41dd1363-1b75-434d-bf58-2fb8e4406a1d`.
- 00:01:18.000 — All 12 rows were skipped. Zapier wrote 0 input rows.
- 00:01:27.000 — Lovable now displays the saved replay report.
- 00:01:34.000 — It shows 12 skips, 0 exceptions and 0 failures.
- 00:01:42.000 — The published v4 Zap is off here. Its saved schedule is daily at 9 AM.
- 00:01:50.000 — It includes weekends and uses the `Asia/Hong_Kong` timezone.
- 00:01:56.000 — The baseline used 82 tasks and the replay used 42: 124 selected tasks on the Zapier Pro trial.
- 00:02:04.000 — An earlier 82-task setup run is excluded because fallback matching was still enabled.
- 00:02:10.000 — This proves two dated fictional runs, not ongoing reliability or future task pricing.

The clip is a retrospective walkthrough with hard cuts. It does not show either run happening live.

The selected baseline is run `01b57ba8-f452-ab39-cc3f-887185666ab4`, batch `80210f58-a647-42ae-8ddf-a31422044c96`. Its native plan accounted for 12 rows: 6 updates, 4 holds and 2 skips, with 10 planned input-row writes. Its completion event was posted once after the row-level work had finished.

The selected replay is run `01b57ba8-7f9d-aa12-209e-60eff41e8524`, batch `41dd1363-1b75-434d-bf58-2fb8e4406a1d`. Zapier accounted for all 12 rows as skips and made 0 input-row writes. The replay completed automatically.

The selected task total is 82 for the baseline plus 42 for the replay: 124 tasks on the Zapier Pro trial, checked on 19 September 2026. An earlier 82-task setup run is visible but excluded because fallback matching was still enabled; its fixture was reset before the selected baseline.

This clip proves this fictional fixture and these two dated runs. It does not establish ongoing reliability, comparative ease or future Zapier task pricing.