Skip to main content
Zapier

Salesforce integration - trigger and connection disruptions

Degraded Lasted 4d 4h · started · Zapier's page

Level
confirmed
Worst impact
Degraded
Down Index
23of 100

What to do

  • Check whether your product depends on Zapier. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4d 4h it lasted.

    Anything that failed between 2026-08-21 09:40 UTC and 2026-08-25 14:20 UTC may need a replay.
  • Subscribe to Zapier's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Zapier 3

  1. investigating

    We’re investigating an issue affecting Salesforce integrations in Zapier. Some customers may see Salesforce connections disconnect, trigger authentication failures, or Zaps held while we investigate. Zap Runs that use Salesforce triggers may be delayed or fail to fire until connections are restored. Other Zap steps and non-Salesforce workflows are not broadly affected based on what we know so far. We’re actively investigating and will provide another update within 60 minutes. If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

    provider

  2. investigating

    We are continuing to investigate an issue affecting Salesforce integrations in Zapier. Some Salesforce connections were invalidated and may show as expired or disconnected in My Apps. How to tell if you’re affected • Go to My Apps: [https://zapier.com/app/connections](https://zapier.com/app/connections "https://zapier.com/app/connections") • If your Salesforce connection shows as expired or disconnected, you’re affected • Zaps that use that Salesforce connection as a trigger (especially polling triggers) may stop firing while the connection is expired • You may also see held Zap runs or trigger authentication failures in Zap History What to do Reconnect the affected Salesforce connection from My Apps. Use a Salesforce user that has permission to authorize the connection in your org. Once reconnected, polling triggers should resume on their normal schedule. Held or missed runs should begin processing again after the connection is healthy. Other impact Zap steps that do not use the affected Salesforce connection, and workflows outside Salesforce, are not broadly affected based on what we know so far. What we’re doing Re-authentication has restored service for customers who have the required Salesforce permissions. We have not deployed a platform-wide fix yet. We are investigating why these connections were invalidated and coordinating with Salesforce. We will provide another update within 60 minutes. If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

    provider

  3. resolved

    Salesforce connections have recovered and authentication errors have returned toward normal levels. Customers should now be able to use their Salesforce integrations normally. We will continue to monitor recovery.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-06799a7bb6

Is Zapier still down?

No, this incident was resolved 2026-08-25 14:20 UTC. For Zapier's live state, see https://down.guide/zapier.

How long did it last?

4d 4h, from 2026-08-21 09:40 UTC to 2026-08-25 14:20 UTC, by the times Zapier posted.

What caused it?

Zapier hasn't published a root cause. If it does, it shows here.

Where does this come from?

Zapier's official status page, https://status.zapier.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.