When a critical Zapier automation stops mid-run and you don't know why, the culprit is often a single expired API connection. Here is exactly why Zapier app connections expire, which apps are most prone to it, and the two-step fix that gets everything running again in under two minutes.
Why Zapier connections expire
Zapier connects to third-party apps using OAuth tokens — short-lived credentials that authenticate the link between Zapier and your app account. Most apps support automatic token renewal in the background, so connections stay active indefinitely.
Some apps, however, enforce a hard expiration policy on their OAuth tokens. When the token expires, the connection breaks. Zapier cannot renew it automatically, and any Zap that relies on that connection will start holding its tasks instead of processing them.
Apps most prone to expiring connections:
- Airtable — personal access tokens and OAuth connections expire and require periodic reauthentication
- Google Workspace apps (Gmail, Google Calendar, Google Sheets, Google Forms) — Google enforces periodic reauthorization regardless of activity
- Microsoft 365 apps (Outlook, OneDrive, Teams) — similar OAuth token refresh requirements
This is not a bug and not something you can prevent entirely. It is simply how those APIs are configured. The goal is to detect it fast and fix it faster.
How to know a connection has expired
Zapier sends an email notification when a connection expires. You can also check manually by going to Apps in the left sidebar of your Zapier dashboard, then selecting the Connections tab. Any expired connection will be flagged there with a clear expiration notice.
In the Connections tab you can also see how many Zaps are actively using each connection — useful for quickly assessing the impact when something breaks.
Pro tip: Check the Connections tab regularly, especially before launching a new onboarding sequence or campaign. A pre-flight check takes 30 seconds and can save hours of cleanup.
How to reconnect in two steps
- Open the expired connection. In the Connections tab, click the app showing the expired status.
- Click "Complete this step" or "Reconnect." Because you are already logged in to the app, Zapier typically needs just one or two button clicks to reestablish the OAuth token.
That's it. The connection is live again. But your Zaps have been holding tasks while it was down — you need to replay those too.
Replaying held tasks after reconnecting
When a connection expires mid-run, Zapier holds the affected tasks rather than dropping them. They queue in Zap History under a "held" status and wait until you clear them.
To replay held tasks:
- Go to Zap History in your Zapier dashboard.
- Zapier will display a prominent notification if you have held tasks, with a button to replay them.
- Click Replay — Zapier re-processes each held task from where it was paused.
The tasks continue from the point they were held, not from scratch, so your data is not duplicated.
How to set up proactive monitoring
Waiting for an email notification is reactive. By the time you read it, your automation may have been down for hours. A better approach is to set up a Zap that sends a Slack message the moment any connection goes offline.
Zapier supports this through its internal alerting capabilities. If your team lives in Slack, a real-time alert means you can catch and fix expired connections in minutes rather than hours — before any members, clients, or downstream workflows notice.
For automations that are critical to your business — onboarding flows, payment processing, client notifications — proactive monitoring is not optional. An expired Airtable connection at 9 pm can cascade into missed follow-ups by morning.
The longer-term fix: reduce dependency on brittle connections
The real solution to connection expiration is reducing how many critical workflows depend on apps with aggressive OAuth policies. Consolidating your data storage into a single platform — rather than bouncing records between a form tool, a database, and a membership platform — reduces the number of potential failure points.
This does not mean abandoning Zapier. It means using it more strategically for the integrations where it adds the most value, rather than as the glue connecting every tool in your stack.
If you are running a complex automation stack and want to audit it for single points of failure, book a free discovery call and let's map it out together.
