rewindex

ChangesZapierConnection errors affecting Salesforce Pardot Zaps

Zapier: Incident updated: Connection errors affecting Salesforce Pardot Zaps

Incident updateNot classified yetChanged status.zapier.com (opens in new tab)
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.

AddedUpdateinvestigating#1
Before: not present
After: Reconnecting your Salesforce Pardot account in Zapier may resolve the connection errors. We have observed recovery for a small number of customers who appear to have reconnected their accounts, but have not yet confirmed that this works for everyone affected. If you are still experiencing errors, try reconnecting your Pardot account. If errors persist or you need help, please contact our support team "contact our support team": https://zapier.com/app/get-help. We are continuing to work with Salesforce on the underlying issue.

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.

History of this incident

YesterdayFriday, October 23Fri, Oct 23

4 incident changes

All Zapier changesZapier profileMarkdownJSON