Four things Zapier does that surprise people
A Zap looks simple, but several documented behaviours decide whether it can be trusted. De-duplication for polling triggers compares item IDs, but only inside one Zap, so two Zaps on one trigger both fire, and it does not stop an action creating a second record. A Zap that errors on 95% of its runs over seven days is switched off by Zapier. Replay comes in two kinds: from history it repeats only errored steps, from the editor it repeats every step. And scheduled Zaps follow the account's time zone, not the Zap's.
Failure is quiet unless someone arranges it
With Autoreplay on, error emails and Zapier Manager triggers wait until the final attempt fails, so the first person to hear may hear about ten and a half hours late. A custom error handler turns the standard emails off. Halted runs, which are deliberate stops often caused by a search finding nothing, are described separately from errors and do not switch the Zap off, so they are easy to overlook. If an important Zap matters daily, someone has to decide who is told, test it with a deliberate failure on a copy, and look at run history from time to time.
Choose the outcome that matches the symptom
Records appear twice: the duplicate-records outcome examines one Zap and one create step. A Facebook Lead Ads Zap shows a sample lead but no live ones: the existing Facebook-to-Salesforce outcome. Fields go missing on the way to Xero: the existing Sheets-to-Xero mapping outcome. Nobody is told when Zaps fail: the failure-alerts outcome covers up to five named automations. Zaps fail now and then and nobody has time to watch: the standing monitor-and-repair service. Each is separate, with its own test and its own boundaries.
- Duplicate records: one Zap, one create step, three synthetic sends and a replay.
- Alerts: a deliberate failure on a copy reaches a shared place and two named people.
- Standing monitoring: weekly review and up to two repairs a month, no response-time promise.
Safe first contact
Describe the Zap's trigger and destination, what you see and when it started. Do not send passwords, API keys, customer lists, invoices or an account invitation. Fit, scope and price are confirmed in writing before any access, and we work on a copy with synthetic data. Every price on the linked outcome pages is an untested proposal, and payment for fixed jobs follows the agreed checks and your sign-off.
Sources and limits
- Zapier: how Zapier handles duplicate data Checked 2026-10-11.
- De-duplication of polling triggers checks only within one Zap, and an action on an app that allows duplicates creates a duplicate record.
- Zapier: troubleshoot errors in Zap workflows Checked 2026-10-11.
- A Zap turns off automatically if 95% of its runs result in errors in the last 7 days; halted runs do not count.
- Zapier: what is replay Checked 2026-10-11.
- Replay from history retries only errored steps, replay from the editor re-runs every step, and error emails wait for the final autoreplay attempt.
- Zapier: schedule Zap workflows Checked 2026-10-11.
- Schedule triggers use the Zapier account's time zone, not the Zap's.