Status: ResolvedThis issue affecting the Close CRM integration has been resolved. Customers should now be able to connect or reconnect their Close account in Zapier normally. We have also replayed impacted delayed/held Zap runs that were paused during the incident. If you’re still seeing errors connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get…
Status: ResolvedWe previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions. The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored. No further action is needed on your end. If a Zap run still shows as fai…
Status: ResolvedThe rollback was successful, and the Google Drive quota errors have been resolved. All Google Drive actions are back to normal. Errored runs have been replayed automatically. Many thanks for your patience while we worked through this. If you have any questions, please reach out to our Support team at zapier.com/get-help: http://zapier.com/get-help.
Status: ResolvedWe've resolved an issue that could cause new BambooHR connections or reconnection attempts to fail with an unclear authentication error and status code 403. The issue stemmed from one of the endpoints we used to verify BambooHR connections becoming unreliable. We've updated our connection check to use a more reliable endpoint and corrected the error messaging so any future authenti…
Status: ResolvedEarlier today, some Translate by Zapier requests failed with 403 “User Rate Limit Exceeded” errors due to a Google Integrations Production Google Cloud billing configuration issue. This has been resolved and we’re seeing successful translations again with no ongoing errors. If you had Zap runs fail during the incident window, you may need to replay those runs to complete processing…
Status: CompleteThe scheduled maintenance has been completed successfully. All services are operating normally.Affected components Polling Triggers (Operational)
Status: ResolvedThis 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 op…
Status: ResolvedThe 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.
Status: ResolvedIssues 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
Status: ResolvedA 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.
Status: ResolvedWe’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-helpAffected components Searches & Writes (Operational)
Status: ResolvedThis 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…
Status: ResolvedOur 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 opera…
Status: ResolvedThis 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…
Status: ResolvedWe 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 ups…
Status: ResolvedThe 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.A…
Status: CompleteWe 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 h…
Status: ResolvedThe 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-helpAffected components Website (Operational)
Status: ResolvedBetween 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 patie…
Status: ResolvedThe 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 t…
Status: ResolvedThe 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-helpAffected compon…
Status: ResolvedA 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://z…
Status: ResolvedShopify 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…
Status: ResolvedThis 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…
Status: ResolvedWe 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…
Status: ResolvedThis 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 work…
Status: ResolvedThe issue causing Code by Zapier steps to return "No response from child process" errors has now been fully resolved. What happened Starting at 14:00 UTC on May 20th, Code by Zapier steps began failing with "No response from child process" errors. Resolution Our engineering team identified the root cause, due to a recent change that routed Team plan Code Steps through a new system.…
Status: ResolvedThe issue affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations has been resolved. Earlier today, an upstream LinkedIn API incident caused intermittent authentication and connection errors. LinkedIn’s platform has recovered, our internal error rates are back to normal, and we’ve replayed impacted tasks where needed. LinkedIn and LinkedIn Ads integra…
Status: ResolvedThe issue preventing some enterprise customers from managing custom actions has been resolved. Customers with over 100 app restrictions were unable to paginate through their custom actions due to a URL formatting issue in our system. This has been corrected and all affected pages now load as expected. No data was lost and no customer action is required. If you're still experiencing…
Status: CompleteSuccessfully completed maintenance. Polling-based triggers have resumed. Missed polls should be picked up.Affected components Polling Triggers (Operational)