Skip to content
OutageDeck

Incident detail

Code by Zapier seeing errors

Code by Zapier seeing errors

Resolved incidentMinor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    We are currently investigating an issue affecting the ability of Code by Zapier steps to run. Starting at approximately 11:00am EST, some Code by Zapier steps began encountering errors, including `CodeStorageExceededException OR ResourceConflictException` This is affecting new Code by Zapier steps, and some existing steps as well. We will provide updates as we make progress on resolving this issue. Thank you for your patience.

  2. Investigating

    We're continuing to investigate reports of errors affecting Code by Zapier steps, including “CodeStorageExceededException” and “ResourceConflictException.” Our engineering team remains actively engaged in identifying the cause of the issue. While we do not have any new information to share at this time, we will provide further updates as our investigation progresses. If you have any questions, please reach out to our support team — [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thank you for your patience and understanding.

  3. Monitoring

    We have pushed out a fix for this Code by Zapier error, and are monitoring the results to ensure that it is working as intended, and fully clearing up those errors. Once we have been able to confirm that this issue is officially resolved, we will update this Status to reflect that. If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thank you again for your patience and understanding.

  4. Resolved

    We have been able to confirm that the update we previously pushed has fully resolved that error. So your Code by Zapier steps should be working as normal, and no longer running into those errors. We are also working on automatically replaying affected Zap runs that were running into this issue. If you are running into this error, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help") Thanks again for your patience while we resolved that.