Resolved -
From Friday, Nov. 15, 10:50 AM UTC, to Saturday, Nov. 16, 10:33 PM UTC, "by Zapier" apps (like Sub-Zap, Delay, Formatter, and Storage) experienced timeout errors.
If Autoreplay was enabled on your Zap, these timeout errors may have resolved themselves. Our team has now replayed all affected Zap runs, so you should no longer see any errors.
If you're still encountering an error, we recommend manually replaying the Zap runs: https://zpr.io/jpDSZb3EWUz6.
Thank you for your patience while we resolved this issue. If you have any further questions, please contact our support team: https://zapier.com/app/get-help.
Nov 18, 12:07 PST
Monitoring -
On Friday, we saw the start of an issue where timeouts were occurring in Delay, Sub-Zap, and Formatter steps.
Our teams have identified the cause, and we have been working on replaying any runs we can that have seen this issue.
As some customers have seen success in this process, If you see any runs returning a timeout error, we advise to try and replay those runs: https://zpr.io/jpDSZb3EWUz6
We should have more soon on this resolution, and we're monitoring to see if any other issues reoccur.
If you do see any issues past that though, please don't hesitate to contact our support team at https://zapier.com/app/get-help.
Nov 18, 10:01 PST
Identified -
We believe we have located the cause of that, and are working with out partners to resolve it as soon as possible.
In the meantime, some users have reported being able to successfully replay these error runs. So if you run into these timeout errors on Delay steps and Sub-Zaps, we advise to try and replay those run: https://zpr.io/jpDSZb3EWUz6
Thank you for your patience, and we apologize for any inconvenience.
Nov 15, 15:40 PST
Investigating -
We are investigating an issue with timeout errors related to Delay and Sub-Zaps. We apologize for any trouble this is causing, and appreciate your patience and understanding during this time.
Nov 15, 13:14 PST
Resolved -
After further investigation, we have confirmed when using an API Request action, API errors may still result in a task completing successfully. This is expected behavior. To view API errors, download the full response data.
We apologize for the confusion and for mistakenly treating this as an incident. If you have any further questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help.
Nov 14, 11:16 PST
Investigating -
We're currently experiencing an issue where steps using "API request (Beta)" Actions that are failing with a 400 error are incorrectly showing a "success" status in the Zap Run history. We are actively investigating this issue. This incident primarily affects the visibility of the success and failure status of your API requests in the Zap Run history. Please note that there's no known workaround at the moment. We understand the importance of accurate status updates and apologize for this inconvenience. As we investigate further, we will continue to provide updates. For any concerns or additional assistance, please don’t hesitate to reach out to our support team.
Nov 13, 08:06 PST
