Starting around 7:30am PST / 2:30pm UTC, we began receiving reports of 500-level “Internal Server Error” messages with the Delay by Zapier app, which prevented some Zap runs from completing as expected. Our engineering team identified the root cause and implemented a fix. The issue has now been fully resolved, and the tasks will be replayed without manual intervention. There was no data loss during this incident. However, because this impacted Delay steps, the timing of some Zap actions during the incident may differ slightly from the configured schedule. We’re continuing to monitor the situation, but everything is now operating normally. If you see any additional errors, please don’t hesitate to let us know.

Starting around 7:30am PST/2:30pm UTC, we began receiving reports of 500-level Internal Server errors with the Delay by Zapier app. This prevented Zap runs from completing as expected. An initial fix has been deployed, and our team is monitoring error rates to ensure all details have been addressed.