Zapier Status

Resolved Field mappings in the Editor are not being retained

Our team is currently investigating an issue where field mappings in the Zap Editor are not being retained.

Resolved Slow processing for some Zap workflows

Some zapier.com pages are failing to load right now. You might see a "503"-code error. Zaps workflows continue to receive new data, but task processing may be temporarily delayed.

Resolved Some Zaps are failing to trigger

Zapier is experiencing an issue where webhooks and polling data are not being processed from external apps as expected. You may be seeing behaviour where triggers are not firing across multiple apps. Our engineering team is currently investigating this issue and it is our number one priority to resolve right now.

Resolved Pardot Triggers and Actions are not working

All Trigger events, Actions and (re)connection attempts to the Pardot integration are currently failing with the following error message: "error=invalid_client_id&error_description=client%20identifier%20invalid"

Resolved Trigger events are delayed and a delay in processing Zap runs

We are currently investigating an issue that is affecting around 2,5% of the Zaps where both instant and polling triggers are delayed, as well as Zap runs not proceeding to the next step immediately. Our engineers are actively working on a resolution. Please accept our sincerest apologies for this inconvenience, we'll keep in touch regularly.