Time: Nov. 21, 2024, 8:50 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Nov. 21, 2024, 8:11 p.m.

Status: Monitoring

Update: A fix has been deployed which now allows data to be imported to Zapier Tables from outside Apps again. You should now be able to import data as expected. Our team is monitoring this fix for any updates.

Time: Nov. 21, 2024, 7:48 p.m.

Status: Investigating

Update: When attempting to import data to Zapier Tables from another app like Google Sheets, an error will be returned and data won't be able to imported. Our team is currently investigating the cause and looking for a fix.

Time: Nov. 21, 2024, 4:58 p.m.

Status: Resolved

Update: All Zap runs have been replayed and there is no data loss. If you have any further questions, please contact our Support Team here: https://zapier.com/app/get-help

Time: Nov. 21, 2024, 3:51 p.m.

Status: Monitoring

Update: We've identified an issue causing intermittent delays with Zap runs of up to an hour. This issue began at 14:24 UTC and was resolved at 15:17 UTC. As a result, timestamps for affected Zap runs during this period may reflect delayed execution times. No data loss occurred during this time. If you have any further questions, please contact our Support Team here: https://zapier.com/app/get-help

Time: Nov. 18, 2024, 8:07 p.m.

Status: Resolved

Update: From Friday, Nov. 15, 10:50 AM UTC, to Saturday, Nov. 16, 10:33 PM UTC, certain apps (Sub-Zaps, Delay, and Formatter) 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.

Time: Nov. 18, 2024, 6:01 p.m.

Status: Monitoring

Update: On Friday, we saw the start of an issue where timeouts were occurring in Delay steps and Sub-Zap steps. Our teams have identified the cause, and we have been working with our partners to resolve this moving forward, and replay any runs we can that have seen this issue. As some customers have seen success in this process, If you see any runs from this timeframe forward to now that have seen this issue, we we advise to try and replay those runs: https://zpr.io/jpDSZb3EWUz6 We should have more soon on this resolution, and we are 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.

Time: Nov. 15, 2024, 11:40 p.m.

Status: Identified

Update: 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.

Time: Nov. 15, 2024, 9:14 p.m.

Status: Investigating

Update: 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.

Time: Nov. 14, 2024, 7:16 p.m.

Status: Resolved

Update: 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. More details on this behavior can be found in our Help Center: https://help.zapier.com/hc/en-us/articles/12899607716493-Set-up-an-API-Request-action#h_01H95JPYYV3DZFJCSXERAMNXNX 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.

Time: Nov. 13, 2024, 4:06 p.m.

Status: Investigating

Update: 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.

Time: Nov. 6, 2024, 11:39 a.m.

Status: Identified

Update: We've identified an issue with the ""New Form Submission in Webflow" trigger, where no sample data is being provided when this trigger is being tested in the Zap editor, and the Zaps are failing to trigger. We are actively working on identifying the root cause of this problem to resolve it as soon as possible. As of now, we do not have an estimated time for resolution, and we regret any inconvenience this issue may cause. We encourage you to contact our Support Team should you need any assistance with other matters: https://zapier.com/app/get-help. We will continue to provide updates on this incident as we have more information. Please stay tuned.