Zapier incident
Code Steps failing with "No response from child process" across Zaps/APIs
Resolved after 1 hour 41 minutes, affecting Instant Triggers and Polling Triggers and 1 more, on May 20, 2026.
The issue causing Code by Zapier steps to return "No response from child process" errors has now been fully resolved. What happened Starting at 14:00 UTC on May 20th, Code by Zapier steps began failing with "No response from child process" errors. Resolution Our engineering team identified the root cause, due to a recent change that routed Team plan Code Steps through a new system. After our team disabled this change, error rates dropped significantly and we have not seen new occurrences since this change. Impact The incident lasted approximately 3 hours and 28 minutes (14:00–17:28 UTC). All affected tasks have been replayed and are now executing successfully. No data was lost, and no action is needed on your side for these runs directly. We apologize for the disruption and appreciate your patience while we resolved this issue. If you do see any further issues with any code steps on your account, please reach out to our team at https://zapier.com/app/get-help
Affected components
Update timeline
- investigating May 20, 2026, 05:16 PM UTC
Starting around 1:55 p.m. UTC, Code by Zapier steps have started failing with the error: "No response from child process" Our team is actively investigating and has engaged the owning engineering team.
- monitoring May 20, 2026, 05:38 PM UTC
What happened: Between approximately 10:00 AM EDT and 1:28 PM EDT today, some Team plan Zaps with Python Code Steps failed with this error: "Error: No response from child process" Who was affected: Team plan customers using Python Code Steps only. Other plan types (Enterprise, Pro, Free) and other Code Step languages were not affected. What we did: We disabled a recent change that routed Team plan Code Steps through a new system. Error rates dropped significantly after this change, and we have not seen new occurrences in the last several minutes. What’s next: We are monitoring for stability and will post a final update shortly. If you need help, contact Support: https://zapier.com/app/get-help
- resolved May 20, 2026, 06:58 PM UTC
The issue causing Code by Zapier steps to return "No response from child process" errors has now been fully resolved. What happened Starting at 14:00 UTC on May 20th, Code by Zapier steps began failing with "No response from child process" errors. Resolution Our engineering team identified the root cause, due to a recent change that routed Team plan Code Steps through a new system. After our team disabled this change, error rates dropped significantly and we have not seen new occurrences since this change. Impact The incident lasted approximately 3 hours and 28 minutes (14:00–17:28 UTC). All affected tasks have been replayed and are now executing successfully. No data was lost, and no action is needed on your side for these runs directly. We apologize for the disruption and appreciate your patience while we resolved this issue. If you do see any further issues with any code steps on your account, please reach out to our team at https://zapier.com/app/get-help
Your product runs on more than Zapier
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services