История сбоев Zapier

1. 13 июля 2026 г. в 17:38 UTCresolved

   Status: Resolved This incident has been resolved. Between approximately 8:00 AM and 9:15 AM CDT (13:00–14:15 UTC), customers may have experienced errors or degraded functionality across multiple Zapier products, including: AI by Zapier, Agents, Chatbots, Forms, Interfaces, Tables, account management, and Zap runs and related automation processing. The underlying issue has been fixed, systems are operating normally, and affected Zap runs and webhook events have been replayed. If you’re still seeing issues, try refreshing the page, logging out and back in, or retrying any failed actions or workflow runs. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we were working on resolving that.

Автоматический перевод официального обновления инцидента.

1. 12 июля 2026 г. в 01:26 UTCresolved

   Status: Resolved The issue impacting AI by Zapier has been mitigated and systems are back to normal. Impact window: Approximately 19:00–22:20 UTC on July 11. We have automatically replayed the affected runs to recover previously failed executions. If you have any remaining questions or are still seeing issues, please contact support at https://zapier.com/get-help.

Автоматический перевод официального обновления инцидента.

1. 8 июля 2026 г. в 20:57 UTCresolved

   Status: Resolved Issues related to Airtable errors are resolved. Any missed triggers and/or actions are replayed. If you have any questions, you can always reach out to our support team here: https://zapier.com/app/get-help

Автоматический перевод официального обновления инцидента.

1. 8 июля 2026 г. в 00:08 UTCresolved

   Status: Resolved A fix has been deployed and we have confirmed no further failures since the rollout. Users signing up for a Teams trial from our pricing page should now receive a Teams trial with access to Teams features. This incident is resolved. If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

Автоматический перевод официального обновления инцидента.

1. 2 июля 2026 г. в 13:10 UTCresolved

   Status: Resolved We’ve confirmed the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. To subscribe to updates about the issue, please contact our support team through this link: https://zapier.com/app/get-help Affected components Searches & Writes (Operational)

1. 26 июня 2026 г. в 16:28 UTCresolved

   Status: Resolved This incident has now been resolved, and all services are operating normally. We’re working with Meta to confirm whether any missed leads will be resent or if further customer action is needed. We’ll share an update once we have more information. Update: We’ve been advised that missed lead notifications from the affected period won’t be resent or backfilled. We understand this may be disruptive for affected customers. To recover missed leads, customers can export a CSV or Excel file from Meta Ads Manager, import it into a Zapier Table, and use Transfer Data to send those leads through their Zap workflow: • Meta export instructions: https://www.facebook.com/business/help/734933888443065 • Zapier Transfer Data instructions: https://help.zapier.com/hc/en-us/articles/8496274335885-Transfer-existing-data-using-a-Zap If you need assistance, or continue to experience any further issues, please reach out to our Support team: https://zapier.com/app/get-help

1. 18 июня 2026 г. в 23:13 UTCresolved

   Status: Resolved Our Engineering team identified and resolved the issue causing degraded performance for Agents. Due to the nature of the issue, we're not able to replay Agent executions during the following incident windows 2026-06-18, between 5:47–7:15PM UTC 2026-06-18, between 8:32 PM–10:08 PM UTC Affected users have been notified via email The incident has been resolved, and Agents is now operating as expected. Affected components Agents (Operational)

1. 18 июня 2026 г. в 18:12 UTCresolved

   Status: Resolved This incident has been resolved. Earlier today, webhook-based triggers experienced processing delays when an unusually high volume of traffic from a third-party integration overwhelmed our shared trigger-processing system. As a result, trigger events across a range of apps were processed more slowly than usual, with delays peaking at around five minutes. We increased our processing capacity to clear the backlog, and the third-party integration also applied mitigations on their end to reduce the excess traffic. Trigger processing has returned to normal and our systems are fully operational. No trigger data was lost during the incident — affected events were delayed rather than dropped, and all delayed events have now been processed. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we were working on resolving that. Affected components Instant Triggers (Operational)

1. 16 июня 2026 г. в 02:36 UTCresolved

   Status: Resolved We have successfully resolved the Facebook Lead Ads integration issue that affected our platform from 12:30pm–4:00pm PDT (7:30pm–11:00pm UTC) on June 16, 2026. During this window, customers experienced failures when connecting or reconnecting Facebook Lead Ads and Facebook Pages integrations, and existing Zaps using these integrations failed to execute. We identified this as an upstream issue with Facebook's APIs, which has since been resolved. All affected workflows have been replayed and are now operating normally. If you continue to experience any issues with your Facebook integrations, please try reconnecting your Facebook app connection or don't hesitate to contact Zapier Support: https://zapier.com/app/get-help.

1. 14 июня 2026 г. в 09:14 UTCresolved

   Status: Resolved The issue affecting access to Zapier template pages has been resolved. Users should now be able to access template pages as expected. We’ve made improvements to help prevent this from happening again and will continue monitoring for stability. If you continue to experience issues accessing templates, please don't hesitate to contact Zapier Support: https://zapier.com/app/get-help. Affected components Website (Operational)

1. 13 июня 2026 г. в 17:19 UTCinvestigating

   Status: Complete We have successfully completed the scheduled maintenance on our Tables service. The upgrade of our underlying database infrastructure is now complete, and all systems are operating normally. Maintenance Summary: • Maintenance window: 4:00 PM - 6:15 PM CET on Saturday, June 13, 2026 • All database instances have been upgraded and are running the latest version • Full functionality has been restored What to Expect: Your Tables service is now fully operational. If you experienced any transient errors or slowness during the maintenance window, these have been resolved. All table operations, including sorting, filtering, and data export, are working as expected. Thank You: We appreciate your patience during this maintenance window. This upgrade improves the performance and stability of our Tables infrastructure for all users. If you have any questions or encounter any issues, please contact our support team. We're back to normal operations. Thank you for your understanding. Affected components Polling Triggers (Operational)

1. 12 июня 2026 г. в 03:51 UTCresolved

   Status: Resolved The issue preventing some users from loading templates is now resolved, and templates are loading normally. If you’re still experiencing issues, please contact Support: http://zapier.com/app/get-help Affected components Website (Operational)

1. 12 июня 2026 г. в 02:33 UTCresolved

   Status: Resolved Between June 9 and June 11, some webhook-triggered Zap runs experienced processing delays of up to 48 hours. All delayed events have since been processed successfully, and no data was lost during this delay. We are implementing additional safeguards to prevent recurrence. If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience. Affected components Instant Triggers (Operational)

1. 8 июня 2026 г. в 18:18 UTCresolved

   Status: Resolved The issue affecting Chatbots has been resolved. Between approximately 11:00 PM and 5:30 AM MST on June 8, 2026, some customers may have experienced failures or timeouts when initializing chats or interacting with embedded chatbots. The issue self-resolved and Chatbots has been operating normally since. Zap Runs and tasks were not affected. No data loss occurred. We are continuing to monitor the service and will take steps to reduce the likelihood of recurrence. If you experienced issues during this window or notice anything still not working, contact Support: https://zapier.com/app/get-help Affected components Chatbots (Operational)

1. 6 июня 2026 г. в 00:36 UTCresolved

   Status: Resolved The issue affecting Zapier Templates pages has been resolved. Some users may have experienced intermittent errors or missing content when loading Templates pages. We’ve taken steps to stop the abnormal traffic driving the problem, and the Templates pages are now operating normally. If you’re still seeing issues, please contact Support: https://zapier.com/app/get-help Affected components Website (Operational)

1. 5 июня 2026 г. в 19:41 UTCresolved

   Status: Resolved A fix has been implemented, and after some monitoring, we're no longer seeing errors when customers are requesting Zap History exports. Any previous export requests during the incident window below have been successfully replayed, so no action is needed. Jun 5th 2026 13:42 - 19:00 UTC If you're still having issues or have questions, please reach out to our Support team at https://zapier.com/app/get-help Affected components Zap History (Operational)

1. 3 июня 2026 г. в 16:00 UTCresolved

   Status: Resolved Shopify Service Restored We're pleased to report that Shopify's services have fully recovered and are operating normally. Our Shopify app is now functioning as expected, and Zap triggers and actions are executing successfully. What happened Between approximately 13:06 UTC and 15:28 UTC on June 3rd, Shopify experienced a widespread outage affecting their Admin API, GraphQL endpoints, and multiple other services. This caused failures in both Zap triggers and Zap actions that rely on Shopify integrations. What we did Once Shopify's services were restored, we automatically replayed all impacted Zap runs to ensure your workflows could complete successfully. Any remaining failed runs will be handled by our automatic replay system. No further action is required from you. We've completed our investigation and confirmed all systems are stable. If you experience any further issues with your Shopify integrations, please don't hesitate to reach out to our support team. Thank you for your patience during this incident.

1. 2 июня 2026 г. в 23:16 UTCresolved

   Status: Resolved This incident has been resolved. The issue that was causing some Code by Zapier steps to fail with the environment variable error has been fixed, and Code by Zapier is now operating normally. Any tasks that were affected during the disruption have been replayed, so no action is needed on your end. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we working on resolving that.

1. 2 июня 2026 г. в 17:26 UTCresolved

   Status: 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 Thanks again for your patience while we resolved that.

1. 21 мая 2026 г. в 03:05 UTCresolved

   Status: Resolved This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected. As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI. Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help