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-26 23: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.

ChangedStatus#1

~~investigating~~

resolved

AddedResolved time#2

not present

2026-10-26 23:02 UTC

AddedUpdateresolved2026-10-26 23:02 UTC#3

not present

This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesforce has remediated their side, but affected connections need to be reconnected. We've deployed a fix on our side so that affected connections now show as expired. To restore your connection, reconnect your Salesforce Pardot account in Zapier. Some Zaps may have been delayed or held, and we're checking that they resume after reconnecting. If your Zaps are still failing after reconnecting, or you need help, please contact our support team: https://zapier.com/app/get-help

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 26
Before captured 19:53 UTC
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on Oct 27, 00:41 UTC. Record hash 427d14dd4200f4b7…
Download proof
Oct 26
After captured 23:03 UTC
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on Oct 27, 00:41 UTC. Record hash 33fd550112a81182…
Download proof

History of this incident

Monday, October 26

2 incident changes

Normal progress
23:03Incident
Incident updateConnection errors affecting Salesforce Pardot Zapsthis change
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 Zaps

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-26 23:03 UTC (change 7 of 7).

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

All Zapier changes Zapier profile Markdown JSON