Istoricul incidentelor Zapier

1. 6 august 2026 la 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.

Traducere automată din actualizarea oficială a incidentului.

1. 28 iulie 2026 la 14:43 UTCresolved

   Stare: Rezolvată Această problemă care afectează integrarea CRM strâns a fost rezolvată. Clienţii ar trebui să poată acum să-şi conecteze sau să-şi reconecteze contul Close din Zapier în mod normal. De asemenea, am reluat testele Zap care au fost întrerupte în timpul incidentului. Dacă încă mai vedeți erori de conectare sau reconectare Închideți, vă rugăm să rejudecați și să contactați Zapier Support la: https://zapier.com/app/get-help.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 20:38 UTCresolved

   Stare: Rezolvată Anterior am raportat erori depășite de cotă care afectează un subset de fluxuri de lucru Zap folosind Google Drive, Google Sheels, Google Docs, Google Slides și Gmail actions. Problema de bază a fost rezolvată. Rulajele Zap afectate au fost reluate, iar fluxurile de lucru care au fost întrerupte din cauza erorilor ridicate au fost restabilite. Nu mai este nevoie de alte acţiuni. Dacă un zap run încă arată că nu a reușit, îl puteți reda din istoria Zap, sau contactați Suportul la Zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 17:50 UTCresolved

   Stare: Rezolvată Reversul a avut succes, iar erorile de cotă Google Drive au fost rezolvate. Toate acțiunile Google Drive au revenit la normal. Rulările greşite au fost reluate automat. Multe mulțumiri pentru răbdare în timp ce am lucrat prin asta. Dacă aveți întrebări, vă rugăm să contactați echipa noastră de sprijin de la Zapier.com/get-help: http://zapier.com/get-help.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 14:38 UTCresolved

   Stare: Rezolvată Am rezolvat o problemă care ar putea cauza noi conexiuni BambusHR sau încercări de reconectare pentru a eșua cu o eroare de autentificare neclară și cod de stare 403. Problema a rezultat dintr-unul dintre obiectivele pe care le-am folosit pentru a verifica conexiunile BambusHR devin nesigure. Ne-am actualizat verificarea conexiunii pentru a utiliza un obiectiv mai fiabil și a corectat mesageria de eroare astfel încât orice viitoare probleme de autentificare va arăta un motiv clar, activ. Ce trebuie să faceţi: • Dacă BambusHR Zaps a continuat să funcţioneze normal pe tot parcursul, nu este necesară nicio acţiune. • Dacă anterior nu aţi reuşit să creaţi o nouă conexiune BambusHR sau să reconectaţi una existentă "reconectaţi una existentă": A se vedea nota de subsol 1. • Dacă nu sunteți sigur dacă conexiunea a fost afectată, vă recomandăm testarea "testului": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-ap-app-connections#01JH3AK296C9MCSX29305AKVZY conexiunea BambusHR "Conexiune BambooHR": https://zapier.com/app/assets/conections?app=BamboHRCLIAPI din setările contului pentru a confirma. Ne cerem scuze pentru orice întrerupere provocată şi vă mulţumim pentru răbdare. Componente afectate Editor Zap (Operațional)

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 12:32 UTCresolved

   Status: Rezolvat mai devreme astăzi, unele Traduce de Zapier cereri nu a reușit cu . . Acest lucru a fost rezolvat și vom vedea traduceri de succes din nou, fără erori în curs de desfășurare. Dacă ați avut Zap rulează eșuează în timpul ferestrei incidentului, s-ar putea să fie necesar să reluați aceste rulaje pentru a finaliza procesarea. Dacă aveți orice probleme în curs de desfășurare, contactați Support: https://zapier.com/app/get-help Mulţumesc pentru răbdare.

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 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.

Traducere automată din actualizarea oficială a incidentului.

1. 12 iulie 2026 la 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.

Traducere automată din actualizarea oficială a incidentului.

1. 8 iulie 2026 la 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

Traducere automată din actualizarea oficială a incidentului.

1. 8 iulie 2026 la 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.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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)