Earlier today we encountered an issue causing delays in some Zap runs and slower performance across the platform. Our Team was able to identify the issue, and pushed a fix.
As a result of this incident there was some loss of data between 11:00 and 17:36 UTC. Our team was unable to recover any lost runs. We apologize for any inconvenience this may have caused.
You should see full functionality returned to the Zap History page as well as your runs. If you run into any further issues or have any questions, feel free to reach out to our Support team.
https://zapier.com/app/get-help
No components marked as affected
Resolved
Earlier today we encountered an issue causing delays in some Zap runs and slower performance across the platform. Our Team was able to identify the issue, and pushed a fix.
As a result of this incident there was some loss of data between 11:00 and 17:36 UTC. Our team was unable to recover any lost runs. We apologize for any inconvenience this may have caused.
You should see full functionality returned to the Zap History page as well as your runs. If you run into any further issues or have any questions, feel free to reach out to our Support team.
https://zapier.com/app/get-help
Monitoring
We’ve temporarily disabled the “Test run” feature while we resolve the root cause and prevent this issue from happening again.
Most users should see Zap executions working as expected. However, Zap History may still be delayed due to the large volume of tasks generated during the incident.
If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help
Identified
We’re currently investigating an issue causing delays in some Zap runs and slower performance across the platform.
Affected users may experience longer execution times or missing steps in Zaps. You may also notice delays in Zap history updates.
Our Team has identified the issue, and we'll provide an update as soon as it's resolved.
