Zapier retries three times, then stops—here's your backup
The kettle’s boiling in a Manchester kitchen, condensation crawling up the window while someone refreshes a Zap history screen for the fourth time in ten minutes, watching a webhook request fail again with no explanation why.
Zapier retries failed webhooks three times over ninety minutes—then quits
Most operators assume Zapier keeps trying until a webhook succeeds. It doesn’t.
When a webhook step fails in Zapier—timeout, 500 error, endpoint offline—Zapier queues a retry. Then another. Then a third. The attempts spread across roughly ninety minutes: immediately, after a few minutes, then after about an hour. If all three fail, Zapier stops. The task shows as errored in your history, you get an email notification if you’ve enabled it, and the data never reaches your endpoint. No escalation, no manual queue, no fourth chance.
This matters when you’re piping form submissions into Airtable, new subscribers into a CRM, or payment webhooks into a fulfilment system. A three-hour server blip, a brief API rate-limit window, or a misconfigured firewall rule can silently drop dozens of records. Zapier’s task history tells you something failed, but by the time you notice, the retry window has closed. You’re left manually reconciling source and destination or accepting the gap.
The fix isn’t hoping your endpoints stay perfect. It’s building a backup: a secondary Zap that watches for errors and logs them to a spreadsheet or Slack channel, a webhook catchment service like Hookdeck that queues and retries independently, or a scheduled daily comparison between your source system and destination to surface missing records. Retry logic keeps automations alive when endpoints flicker. Knowing when it stops keeps you from assuming everything landed.
TACTIC
ConvertKit automations can trigger the same action twice
ConvertKit’s visual automation builder lets you stack triggers and conditions—but certain configurations fire the same email or tag twice for a single subscriber action. It happens when multiple paths converge, when a tag-based trigger overlaps with a form submission, or when a subscriber re-enters a sequence you thought was one-time-only. The duplicate sends look identical in your sent log, subscribers get confused, and your open rates compress because the second email arrives before they’ve finished the first. The fix is structural: design automations with explicit exit rules, use filters to block re-entry, and test every branch with a dummy subscriber before going live.
WORTH READING
WordPress staging sync skips uploads and user data
Most managed WordPress hosts offer one-click staging environments—copy your production site, test changes, push back when ready. But the sync is selective. Staging-to-live pushes typically transfer database schema, theme files, and plugin code. They skip the uploads folder, user accounts created during testing, form submissions, and analytics logs. If you’ve uploaded images, PDFs, or course videos to staging, those files won’t appear on production after the merge. If you’ve created test users or captured real leads through a staging URL, that data stays orphaned. The solution is knowing what transfers automatically and what requires manual migration before you click “Push to Live”.
READER QUESTION
Why published sponsorship rates rarely match closed deals
Most newsletter sponsorship rate cards publish a single CPM or flat fee—$50 per thousand subscribers, $800 for a dedicated send. But deals rarely close at card rate. Sponsors negotiate volume discounts, ask for bonus placements, request partial refunds if open rates dip, or barter down when your list skews outside their target demo. Annual contracts typically land 15–30% below published rates. First-time sponsors pay closer to card, but they also ghost more often. The gap between what you publish and what you invoice exists because rate cards are negotiation anchors, not final prices. Knowing the spread helps you forecast revenue accurately and decide when to hold firm and when to flex.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.