Historial de interrupciones de Zapier

1. August 6, 2026 at 12:28 PM UTCresolved

   Status: Resolved We have successfully resolved the Salesforce connection issues that affected some of our customers earlier today. What Happened A recent update to our Salesforce integration caused authentication failures for users who were automatically migrated to the new version. Customers attempting to connect or reconnect their Salesforce accounts received an error message. What We Did Our team quickly identified the root cause, stopped further migrations, and rolled back all affected users to a previous working version. We then systematically reactivated all affected Salesforce connections and replayed any impacted Zap runs to ensure no data was lost. Resolution All Salesforce connections have been restored and are now working normally. Your Zaps should resume processing automatically. If you experienced any issues earlier today, your connections are now active and ready to use. Thank You We sincerely apologize for this disruption and appreciate your patience as we worked to resolve this issue. If you have any questions or continue to experience problems, please contact our support team at https://zapier.com/app/get-help. Thank you for your continued trust in Zapier.

1. July 28, 2026 at 2:43 PM UTCresolved

   Estado: Resuelvado Se ha resuelto esta cuestión que afecta a la integración de Close CRM. Los clientes deben ahora poder conectar o reconectar su cuenta Cerrar en Zapier normalmente. También hemos reinterpretado las carreras de Zap retardadas o retenidas que se detuvieron durante el incidente. Si sigues viendo errores que conectan o reconectan Close, por favor vuelva a entrar y ponerse en contacto con Zapier Support en: https://zapier.com/app/get-help.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 8:38 PM UTCresolved

   Estado: Resuelvado Anteriormente reportamos errores de comparación de cuotas que afectan a un subconjunto de flujos de trabajo de Zap usando Google Drive, Google Sheets, Google Docs, Google Slides y acciones de Gmail. Se ha fijado la cuestión subyacente. Se han reproducido las carreras de Zap afectadas, y se han restaurado los flujos de trabajo que se detuvieron debido a errores elevados. No se necesita más acción al final. Si una carrera de Zap todavía muestra como fallido, puede reproducirlo desde su historia de Zap, o contactar con Soporte en zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 5:50 PM UTCresolved

   Estado: Resuelvado El retroceso fue exitoso, y los errores de cuota de Google Drive se han resuelto. Todas las acciones de Google Drive vuelven a la normalidad. Se han reproducido automáticamente las carreras de error. Muchas gracias por su paciencia mientras trabajamos a través de esto. Si tiene alguna pregunta, comuníquese con nuestro equipo de apoyo en zapier.com/get-help: http://zapier.com/get-help.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 2:38 PM UTCresolved

   Estado: Resuelvado Hemos resuelto un problema que podría causar nuevas conexiones BambooHR o intentos de reconexión de fracasar con un error de autenticación y código de estado 403. La cuestión surgió de uno de los puntos finales que usamos para verificar que las conexiones de BambooHR se vuelven inconfiables. Hemos actualizado nuestro cheque de conexión para utilizar un punto final más fiable y corrigido el mensaje de error para que cualquier problema de autenticación futuro muestre una razón clara y factible. Lo que necesitas hacer: • Si tus Zaps BambooHR han seguido corriendo normalmente a lo largo de todo, no se requiere ninguna acción. • Si usted no pudo crear una nueva conexión BambooHR o reconectar una existente "reconectar una existente": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, inténtelo de nuevo, esto debería tener éxito. • Si no está seguro de si su conexión fue afectada, le recomendamos probar "testing": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY su conexión BambooHR": https/BambooHRconnecto Nos disculpamos por cualquier perturbación que esto causó y gracias por su paciencia. Componentes afectados Zap Editor (Operational)

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 12:32 PM UTCresolved

   Estado: Resuelto Hoy en día, algunas solicitudes de Traducir por Zapier fallaron con 403 errores “User Rate Limit Exceed” debido a un problema de configuración de facturación de Google Cloud de Google Integrations Production. Esto ha sido resuelto y estamos viendo traducciones exitosas de nuevo sin errores en curso. Si hubieras fallado las carreras de Zap durante la ventana del incidente, es posible que necesites reproducirlas para completar el procesamiento. Si experimenta algún problema en curso, contacte con Support: https://zapier.com/app/get-help Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 5:38 PM 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. July 12, 2026 at 1:26 AM 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. July 8, 2026 at 8:57 PM 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. July 8, 2026 at 12:08 AM 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. July 2, 2026 at 1:10 PM 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. June 26, 2026 at 4:28 PM 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. June 18, 2026 at 11:13 PM 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. June 18, 2026 at 6:12 PM 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. June 16, 2026 at 2:36 AM 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. June 14, 2026 at 9:14 AM 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. June 12, 2026 at 3:51 AM 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. June 12, 2026 at 2:33 AM 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. June 8, 2026 at 6:18 PM 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. June 6, 2026 at 12:36 AM 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)