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: We have confirmed that this is an upstream issue with the Pardot service and are monitoring its status. There is no confirmed recovery time yet. We are assessing whether any trigger activity was missed during the disruption and whether additional recovery steps will be needed. Once connections recover, we will verify that affected Zaps resume and check whether delayed or held runs need additional attention. We will let you know if any action is required from your team. If you need assistance in the meantime, please contact our support team "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.

History of this incident

YesterdayFriday, October 23Fri, Oct 23

4 incident changes

All Zapier changesZapier profileMarkdownJSON