Historique des pannes de Zapier

1. 6 août 2026 à 12:28 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.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 28 juillet 2026 à 14:43 UTCresolved

   État : résolu Ce problème touchant l'intégration de CRM étroite a été résolu. Les clients devraient maintenant être en mesure de connecter ou de reconnecter leur compte Close à Zapier normalement. Nous avons également rejoué des pistes de Zap retardées/en attente qui ont été interrompues pendant l'incident. Si vous voyez toujours des erreurs de connexion ou de reconnexion Close, veuillez réessayer et contacter Zapier Support à l'adresse suivante : https://zapier.com/app/get-help.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juillet 2026 à 20:38 UTCresolved

   État : résolu Nous avons déjà signalé des erreurs hors quota affectant un sous-ensemble de workflows Zap utilisant Google Drive, Google Sheets, Google Docs, Google Slides et les actions Gmail. La question sous-jacente a été réglée. Les runs Zap touchés ont été rejoués, et les workflows qui ont été interrompus en raison d'erreurs élevées ont été restaurés. Aucune autre mesure n'est nécessaire à votre fin. Si un exercice Zap affiche toujours comme échoué, vous pouvez le rejouer à partir de votre historique Zap, ou contacter Support à zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juillet 2026 à 17:50 UTCresolved

   État : résolu Le retour a été réussi, et les erreurs de quota Google Drive ont été résolues. Toutes les actions Google Drive sont de retour à la normale. Les lancers d'erreur ont été rejoués automatiquement. Merci beaucoup pour votre patience pendant que nous avons travaillé là-dessus. Si vous avez des questions, veuillez contacter notre équipe de soutien à l'adresse zapier.com/get-help: http://zapier.com/get-help.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juillet 2026 à 14:38 UTCresolved

   État : résolu Nous avons résolu un problème qui pourrait causer de nouvelles connexions BambooHR ou des tentatives de reconnection pour échouer avec une erreur d'authentification et un code d'état peu clair 403. Le problème découle de l'un des paramètres utilisés pour vérifier que les connexions BambooHR deviennent peu fiables. Nous avons mis à jour notre vérification de connexion pour utiliser un paramètre plus fiable et corrigé la messagerie d'erreur afin que tout problème d'authentification futur montre une raison claire et actionnable. Ce que vous devez faire: • Si votre BambooHR Zaps a continué à fonctionner normalement tout au long, aucune action n'est nécessaire. • Si vous n'étiez pas en mesure de créer une nouvelle connexion BambooHR ou de reconnecter une connexion existante « reconnecter une connexion existante » : https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, veuillez réessayer, ceci devrait maintenant réussir. • Si vous ne savez pas si votre connexion a été affectée, nous vous recommandons de tester "test": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY votre connexion BambooHR "connection BambooHR": https://zapier.com/app/assets/connections?app=BambooHRCLIAPI à partir des paramètres de votre compte pour confirmer. Nous nous excusons de toute perturbation de cette situation et vous remercions de votre patience. Composants affectés Zap Editor (opérationnel)

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 21 juillet 2026 à 12:32 UTCresolved

   Statut: Résolue Plus tôt aujourd'hui, certaines requêtes Traduire par Zapier ont échoué avec 403 -Dépassé la limite de taux d'utilisateur en raison d'un problème de configuration Google Cloud Production. Ceci a été résolu et nous voyons à nouveau des traductions réussies sans erreurs en cours. Si Zap a échoué pendant la fenêtre d'incident, vous devrez peut-être rejouer ces lancers pour terminer le traitement. Si vous rencontrez des problèmes en cours, contactez Support: https://zapier.com/app/get-help Merci de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 13 juillet 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.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 12 juillet 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.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 juillet 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

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 juillet 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.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 juillet 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 juin 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 juin 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 juin 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 juin 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 juin 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. 12 juin 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 juin 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 juin 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 juin 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)