Changes Zapier Connection errors affecting Salesforce Pardot Zaps

Zapier: Incident updated: Connection errors affecting Salesforce Pardot Zaps

Incident updateNormal progress (rule, 100%)Changed 2026-10-24 14:03 UTCstatus.zapier.com

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Zapier removed; blue is what they added. Muted text is unchanged context.

AddedUpdateinvestigating2026-10-24 14:00 UTC#1

not present

Some Salesforce Pardot Zaps continue to experience connection errors, preventing them from running or delaying workflows. We are continuing to work with our partner, Salesforce, to obtain full confirmation of the underlying issue and the steps needed for recovery. If you are affected, try reconnecting your Salesforce Pardot account in Zapier. Reconnecting has helped some customers restore their connections and may resolve the errors, but we have not confirmed that it works for everyone affected. If errors persist after reconnecting, or you need help, please contact our support team "contact our support team": https://zapier.com/app/get-help. We do not yet have a confirmed recovery time.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Oct 23
Before captured 22:23 UTC
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on Oct 24, 00:41 UTC. Record hash 9dc882392eb464c6…
Download proof
Oct 24
After captured 14:03 UTC
In the 2026-10-24 checkpoint, timestamped by FreeTSA and DigiCert on Oct 25, 00:41 UTC. Record hash 5ee93a8033094eea…
Download proof

History of this incident

Monday, October 26

2 incident changes

Normal progress
23:03Incident
Incident updateConnection errors affecting Salesforce Pardot Zaps
Normal progress
19:53Incident
Incident updateConnection errors affecting Salesforce Pardot Zaps

Saturday, October 24

1 incident change

Normal progress
14:03Incident
Incident updateConnection errors affecting Salesforce Pardot Zapsthis change

Friday, October 23

4 incident changes

Normal progress
22:23Incident
Incident updateConnection errors affecting Salesforce Pardot Zaps
Normal progress
16:23Incident
Incident updateConnection errors affecting Salesforce Pardot Zaps
Normal progress
12:13Incident
Incident updateConnection errors affecting Salesforce Pardot Zaps
Outage
10:50Major incident
Connection errors affecting Salesforce Pardot Zaps
Zapier reported a major incident starting 2026-10-23 10:50 UTC: connection errors prevented some Salesforce Pardot Zaps from running, while other Pardot connections ran normally. The incident was still open when archived (open for 0 min at the last update); Zapier was investigating and checking recovery of affected connections and delayed Zap runs.

Cite this

Incident updated: Connection errors affecting Salesforce Pardot Zaps on Zapier’s status page, changed 2026-10-24 14:03 UTC (change 5 of 7).

Title: Incident updated: Connection errors affecting Salesforce Pardot Zaps
Vendor: Zapier
Date: 2026-10-24 14:03 UTC
URL: https://rewindex.com/change/r6b54a20f509f29

All Zapier changes Zapier profile Markdown JSON