Zapier

We are currently investigating intermittent Internal Server Errors (HTTP 500) affecting Zaps. Some customers may experience errors when editing their Zaps, and we understand how disruptive this is to your workflows. Our engineering teams are actively working to identify and resolve the root cause. We will provide updates as we learn more. Thank you for your patience.

A previous incident on March 18 "previous incident on March 18": https://status.zapier.com/incidents/01KKZAYF71JFXMX65DDWC33PXP caused Zaps using Google Sheets and Google Drive to pause. While that incident was resolved, some affected Zaps were not restored and remain paused. If your Google Sheets or Google Drive Zaps are currently paused, you will need to turn them back on manually. You can check for affected Zaps directly using this filtered view of your paused Google Sheets and Google Docs Zaps "this filtered view of your paused Google Sheets and Google Docs Zaps": https://zapier.com/app/assets/zaps?app=GoogleSheetsV2CLIAPI%2CGoogleDocsV2CLIAPI&status=off. Look for Zaps that were paused between March 18 and March 19, 2026 and turn on any that should be active. If your Zaps missed data while they were paused, you can import the missing records using Transfer existing data using a spreadsheet "Transfer existing data using a spreadsheet": https://help.zapier.com/hc/en-us/articles/21695863326861-Transfer-existing-data-using-a-spreadsheet. If you need help or have questions, contact our support team at https://zapier.com/app/get-help.

TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently in progress

We‘re investigating intermittent task failures affecting some Zaps that occurred between March 24 and March 26, 2026. We have identified the root cause as exhausted database connections in our developercli service and have deployed a fix. What happened: Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed intermittently due to exhaustion of the database connection pool. This affected a subset of customer Zaps, though the majority of our platform remained operational. Current status: The underlying issue has been resolved. We‘re currently replaying affected tasks to ensure they complete successfully. Most tasks with auto-replay enabled are being automatically reprocessed. What you may have experienced: If you use developercli-dependent Zaps, you may have seen task failures during this window. We apologize for any disruption this caused to your workflows. Next steps: We‘re completing task replays and will provide a full update once all affected tasks have been reprocessed. We do not expect any further issues. Thank you for your patience as we work through this issue. If you have any questions, please reach out to our support team - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

We’re investigating an issue impacting a subset of customers where payments may fail during checkout, subscription renewals, or plan changes. Customers may see a generic “unable to process payment” error and invoices may remain unpaid due to repeated failed attempts. If you are seeing this error, re-adding your payment method should resolve the issue and allow you to checkout. Our team is working to resolve this error internally as well. If you have any questions feel free to reach out to our support team. - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

We're aware of public reports regarding a supply chain issue affecting specific LiteLLM package versions published to PyPI. Out of caution, we reviewed our environments and confirmed that the LiteLLM versions deployed by Zapier are not among the affected versions reported publicly. At this time, we have no evidence of impact to customer data, Zapier systems, or services. We also confirmed that no automated systems could upgrade to the affected versions and found no other related deployments in our environment. We will continue monitoring the situation and will share updates if anything changes. If you have any questions, please reach out to our support team - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

We’re investigating an issue where some users are unable to add or remove tools on Zapier MCP servers. Affected users may see a message prompting them to “switch to the account that owns the server” and may be disconnected after authentication. Our team has identified and reproduced the issue and is actively working on a fix. We’ll share another update as we learn more.

We're currently investigating an issue where users are seeing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and when attempting to create new connections. We will provide an updated status by 2:30 PM PST

We have identified the cause of an ongoing issue affecting Google integrations, including Google Sheets, with some impact to Google Drive and Google Docs. Users may experience intermittent connection or authentication errors, which can result in failed Zap runs or workflows not triggering as expected. In some cases, Zap runs may be delayed or temporarily held. Our team is actively working on mitigation to restore stability. We are seeing early signs of improvement, but some users may continue to experience intermittent issues while mitigation efforts are ongoing. We appreciate your patience as we continue to resolve this issue. We’ll provide further updates as progress continues.

We are currently investigating delays affecting the display of Zap run history, and errors on the Zap Usage page. You may be seeing a delay in loading times on both pages. Zap executions are running normally and completing as expected. We appreciate your patience as we work through this issue. We'll provide updates as the situation progresses.

We are currently investigating delays affecting the display of Zap run history. You may be seeing a delay in your runs showing up in your Zap history at this time. Zap executions are running normally and completing as expected, but there may be a delay of up to several minutes before runs appear in your Zap history view. We appreciate your patience as we work through this issue. We'll provide updates as the situation progresses.

We’re currently investigating an issue affecting checkout where the payment and tax modals may not appear correctly. Self-serve customers who need to add or update payment or tax information during checkout may be unable to complete checkout. Workaround: If you can’t add a card during checkout, you can add a payment method from the billing settings page and then return to checkout. We’ll share another update as soon as we have more information.

Our Engineering team is aware of reports of users receiving "Copilot isn't responding right now" or "Connection refused" errors and are deploying a fix for the issue. We will continue to monitor for any abnormal responses as we roll out a fix.

We are investigating reports of increased errors and actions not functioning for customers utilizing Zapier MCP alongside Claude CoWork. Our Engineering team is working to identify and resolve the issue. If you're affected by this, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

We are aware of reports that new app connections can't be created when using OAuth. Users will see a 404 error or a blank page when trying to authorize new app connections that require OAuth. Existing app connections are not affected. We'll keep you updated as we work to resolve the issue. If you find yourself impacted, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help