Störungsverlauf von Zapier

1. 6. August 2026 um 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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 28. Juli 2026 um 14:43 UTCresolved

   Status: gelöst Dieses Problem, das die Close CRM-Integration betrifft, wurde behoben. Kunden sollten nun in der Lage sein, ihr Close-Konto in Zapier normal zu verbinden oder wieder zu verbinden. Wir haben auch betroffene verzögerte/gehaltene Zap-Läufe wiederholt, die während des Vorfalls angehalten wurden. Wenn Sie immer noch Fehler beim Verbinden oder Wiederverbinden von Close sehen, versuchen Sie es bitte erneut und kontaktieren Sie den Zapier Support unter: https://zapier.com/app/get-help.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 20:38 UTCresolved

   Status: gelöst Wir haben zuvor quotenüberschrittene Fehler gemeldet, die eine Teilmenge von Zap-Workflows mit Google Drive, Google Sheets, Google Docs, Google Slides und Gmail-Aktionen betreffen. Das zugrunde liegende Problem wurde behoben. Betroffene Zap-Läufe wurden wiederholt und Workflows, die aufgrund erhöhter Fehler pausiert wurden, wurden wiederhergestellt. Es sind keine weiteren Maßnahmen an Ihrem Ende erforderlich. Wenn ein Zap-Lauf weiterhin als fehlgeschlagen angezeigt wird, können Sie ihn aus Ihrem Zap-Verlauf abspielen oder sich an den Support unter zapier.com/get-help "zapier.com/get-help" wenden: http://zapier.com/get-help.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 17:50 UTCresolved

   Status: gelöst Das Rollback war erfolgreich und die Quotenfehler von Google Drive wurden behoben. Alle Google Drive-Aktionen sind wieder normal. Fehlerhafte Läufe wurden automatisch wiederholt. Vielen Dank für Ihre Geduld, während wir das durchgearbeitet haben. Bei Fragen wenden Sie sich bitte an unser Support-Team unter zapier.com/get-help: http://zapier.com/get-help.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 14:38 UTCresolved

   Status: gelöst Wir haben ein Problem behoben, das dazu führen könnte, dass neue BambooHR-Verbindungen oder Wiederverbindungsversuche mit einem unklaren Authentifizierungsfehler und Statuscode 403 fehlschlagen. Das Problem rührte von einem der Endpunkte her, mit denen wir überprüften, dass BambooHR-Verbindungen unzuverlässig wurden. Wir haben unsere Verbindungsüberprüfung aktualisiert, um einen zuverlässigeren Endpunkt zu verwenden, und die Fehlermeldungen korrigiert, damit zukünftige Authentifizierungsprobleme einen klaren, umsetzbaren Grund zeigen. Was Sie tun müssen: • Wenn Ihre BambooHR Zaps weiterhin normal laufen, sind keine Maßnahmen erforderlich. • Wenn Sie zuvor nicht in der Lage waren, eine neue BambooHR-Verbindung zu erstellen oder eine bestehende Verbindung wieder herzustellen, "eine bestehende Verbindung wieder herstellen": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, bitte versuchen Sie es erneut, dies sollte jetzt erfolgreich sein. Wenn Sie sich nicht sicher sind, ob Ihre Verbindung betroffen war, empfehlen wir Ihnen, "Testing" zu testen: https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY Ihre BambooHR-Verbindung "BambooHR connection": https://zapier.com/app/assets/connections?app=BambooHRCLIAPI aus Ihren Kontoeinstellungen zu bestätigen. Wir entschuldigen uns für jede Störung, die dadurch verursacht wurde, und danken Ihnen für Ihre Geduld. Betroffene Komponenten Zap Editor (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 12:32 UTCresolved

   Status: Einige Translate by Zapier-Anfragen sind heute mit 403 „User Rate Limit Exceeded-Fehlern aufgrund eines Google Integrations Production-Konfigurationsproblems mit Google Cloud gescheitert. Dies wurde behoben und wir sehen wieder erfolgreiche Übersetzungen ohne fortlaufende Fehler. Wenn Zap-Läufe während des Ereignisfensters fehlgeschlagen sind, müssen Sie diese Läufe möglicherweise wiederholen, um die Verarbeitung abzuschließen. Wenn Sie Probleme haben, wenden Sie sich an den Support: https://zapier.com/app/get-help Vielen Dank für Ihre Geduld.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. Juli 2026 um 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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juli 2026 um 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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 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

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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)