Some parts of Zapier.com are returning 500 errors, Zap runs are not affected

Our engineering team had deployed a fix and resolved the process that caused the issue. The system should be stable now and users should be able to access the Zap Editor, edit Zaps, and publish their Zaps without errors.

If you have any questions or still encounters similar errors, feel free to reach out to Zapier Support: https://zapier.com/app/get-help.

Our engineering team identified and resolved the process that caused the issue. The system has now stabilized, and normal service has resumed.

We are finalizing outreach to affected customers and will continue to monitor closely. We sincerely apologize for any disruption this caused and are taking steps to prevent recurrence.

If you have any questions, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Zapier is currently experiencing an incident, and the root cause has been identified. It is having a widespread impact. Some notable impacts have been:

- The Zap Editor can't be accessed, and no Zaps can be edited at this time
- Users on multiple accounts can't swap between them

This incident is not impacting hooks and the Zap function remains stable.

Thanks for your patience while implementing a fix!