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.

Time: Oct. 25, 2024, 5:04 a.m.

Status: Resolved

Update: Maintenance has been completed successfully. Zaps that tried to run during the maintenance window will now resume. Please feel free to reach out to Zapier Support with any questions or concerns! https://zapier.com/app/get-help

Time: Oct. 24, 2024, 9:28 p.m.

Status: Investigating

Update: On Fri, 25 Oct at 04:00 UTC, Tables, Interfaces, and Chatbots will undergo maintenance. This maintenance should last around 30 minutes, during which time you may see errors with Tables, Interfaces, and Chatbots while they are down and being worked on. We apologize for any inconvenience. If have any questions, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Time: Oct. 25, 2024, 11:09 a.m.

Status: Resolved

Update: We have addressed the issue affecting users' interaction with Facebook Lead Ads on Zapier. Previously, users encountered an error message: "Unsupported get request. Object with ID 'XXXXX' does not exist, cannot be loaded due to missing permissions, or does not support this operation." This issue also affected testing of Facebook Lead Ads triggers, where users might have seen this error: "Error Code: Error while retrieving: The app returned "A test lead was already created for this leadgen form. Delete the existing lead before creating a new one. To retrieve the lead id, use the GET call on /test_leads edge."." Please note that this incident only impacted users utilizing Facebook Lead Ads. Our team has reached out and worked with Meta to resolve the issue and replayed tasks for Facebook Lead Ads. Tasks for Facebook Lead Ads(For Business Admins) and Facebook Conversions will be replayed by Friday, 25th Oct, 2024. Any users still encountering issues are advised to reach out to our support team at: https://zapier.com/app/get-help. We appreciate your understanding and patience during this incident. If you run into any further issues, kindly reach out to us for assistance.

Time: Oct. 24, 2024, 7:22 p.m.

Status: Monitoring

Update: Meta has implemented a fix for the issue. Our team is actively monitoring the situation to ensure it is fully resolved. All affected runs have been successfully replayed. If you do experience any more problems, please don't hesitate to reach out to the support team here: https://zapier.com/app/get-help

Time: Oct. 24, 2024, 10:08 a.m.

Status: Identified

Update: Due to an error, the Status page was set to resolved. However, we are still investigating an ongoing issue affecting Facebook Lead Ads on Zapier. The problem is causing hydration errors, and we have traced this to a specific error message: "Unsupported get request. Object with ID 'XXXXX' does not exist, cannot be loaded due to missing permissions, or does not support this operation." Users may encounter this issue while attempting to interact with Facebook Lead Ads. Please note that this incident does not impact users who are not utilizing Facebook Lead Ads. 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.