Zapier Outage History

Started Jul 22, 2026, 02:19 PM UTC· resolved Jul 22, 2026, 05:50 PM UTC

1. identified Jul 22, 2026, 02:19 PM UTC

   Our Engineering has identified an issue with the Google Drive integration hitting intermittent 403 - Quota Exhausted errors across all actions. The team is working on implementing a fix. If you have any questions, please reach out to our Support team at zapier.com/get-help.

2. monitoring Jul 22, 2026, 04:34 PM UTC

   Our Engineering implemented a fix by rolling back an update that caused the elevated errors. All Zap workflows using Google Drive actions will continue to execute correctly. Errored runs will be replayed automatically. We continue to monitor performance to confirm all error rates have returned back to baseline. If you have any questions, please reach out to our Support team at zapier.com/get-help.

3. resolved Jul 22, 2026, 05:50 PM UTC

   The 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.

Read the full incident report →

Started Jul 21, 2026, 01:35 PM UTC· resolved Jul 22, 2026, 02:38 PM UTC

1. investigating Jul 21, 2026, 01:35 PM UTC

   We've received reports of customers being unable to create new BambooHR connections, or test existing BambooHR connections, within the Zap Editor. Attempts at either result in an error code with response status code 403. We are working with BambooHR to identify the cause of the error and resolve this as quickly as possible.

2. monitoring Jul 21, 2026, 08:29 PM UTC

   We've identified the cause the issue preventing users from creating new BambooHR connections or testing/updating existing BambooHR connections. We've released an update the we believe will address this issue, and will continue to monitor to confirm the issue is resolved.

3. resolved Jul 22, 2026, 02:38 PM UTC

   We'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 authentication issues will show a clear, actionable reason. What you need to do: • If your BambooHR Zaps have continued running normally throughout, no action is required. • If you were previously unable to create a new BambooHR connection or reconnect an existing one "reconnect an existing one": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6, please try again, this should now succeed. • If you're unsure whether your connection was affected, we recommend testing "testing": https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK296C9MCSX29305AKVZY your BambooHR connection "BambooHR connection": https://zapier.com/app/assets/connections?app=BambooHRCLIAPI from your account settings to confirm. We apologize for any disruption this caused and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 09:25 AM UTC· resolved Jul 21, 2026, 12:32 PM UTC

1. investigating Jul 21, 2026, 09:25 AM UTC

   We are currently investigating elevated error rates affecting the Translate by Zapier integration. Starting at approximately 2:00pm UTC on July 20, 2026, users of this integration have been experiencing 403 "User Rate Limit Exceeded" errors when attempting to use the translation features. What's Happening Our investigation has identified that the Google Cloud Translation API v2 is returning rate limit errors for requests from the Translate by Zapier integration. This is causing approximately 88% of translation requests to fail. We have confirmed that this issue originates from Google's API, not from Zapier's systems. Who's Affected Affected users may see failed translation steps in their Zaps, though the errors are not automatically disabling workflows. What We're Doing Our engineering team is actively investigating mitigation options. We will provide updates as we make progress. Next Update We expect to have more information soon. We appreciate your patience as we work to resolve this issue.

2. resolved Jul 21, 2026, 12:32 PM UTC

   Earlier 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. If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started Jul 13, 2026, 01:33 PM UTC· resolved Jul 13, 2026, 05:38 PM UTC

1. investigating Jul 13, 2026, 01:33 PM UTC

   We are investigating an issue causing elevated authentication failures (401s) across multiple Zapier products and services. Our engineering team is actively investigating, and we will provide another update as we learn more. If you need help, contact Support: https://zapier.com/app/get-help

2. monitoring Jul 13, 2026, 02:22 PM UTC

   We applied a fix and are seeing authentication failures and related errors return to normal across affected Zapier products and services. We are continuing to monitor closely to ensure the recovery is sustained. If you need help, contact Support: https://zapier.com/app/get-help

3. resolved Jul 13, 2026, 05:38 PM UTC

   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.

Read the full incident report →

Started Jul 11, 2026, 10:10 PM UTC· resolved Jul 12, 2026, 01:26 AM UTC

1. investigating Jul 11, 2026, 10:10 PM UTC

   Investigating — We are investigating an issue affecting AI by Zapier steps in Zaps, which is causing errors for some customers. Affected customers may encounter the following error: DriverAdapterError Our team has identified the issue and is actively working to restore service as quickly as possible. We will provide another update as soon as we have more information.

2. monitoring Jul 11, 2026, 10:51 PM UTC

   Monitoring — A fix has been implemented, and we are seeing recovery across AI by Zapier. We are continuing to monitor the service closely to ensure stability. We will continue monitoring and provide another update once we have confirmed the issue is fully resolved.

3. resolved Jul 12, 2026, 01:26 AM UTC

   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.

Read the full incident report →

Started Jul 08, 2026, 08:08 PM UTC· resolved Jul 08, 2026, 08:57 PM UTC

1. investigating Jul 08, 2026, 08:08 PM UTC

   We are noticing issues related to the Airtable integration. This might result in increased 4XX errors in Zaps or missed triggers. If you are running into these issues, please reach out to our support team here: https://zapier.com/app/get-help

2. monitoring Jul 08, 2026, 08:28 PM UTC

   We’ve confirmed the trigger-side impact from the Airtable incident has healed, and are looking into replaying any missed triggers.

3. resolved Jul 08, 2026, 08:57 PM UTC

   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

Read the full incident report →

Started Jul 07, 2026, 05:03 PM UTC· resolved Jul 08, 2026, 12:08 AM UTC

1. investigating Jul 07, 2026, 05:03 PM UTC

   We have reports that users who sign up for a Team trial are actually enrolled in a Pro trial. This means that Teams features are not available during the trial period. Our Engineering team is aware of the issue and is working to resolve it. We'll continue to give updates as we make progress.

2. investigating Jul 07, 2026, 07:19 PM UTC

   We’re aware an issue where some users who sign up for a Teams trial are instead enrolled in a Pro trial. As a result, Teams features may not be available during the trial period. Our engineering team is continuing to investigate this issue and is working to resolve it. We’ll share another update by 2:15pm PT / 21:15 UTC. If you're experiencing any other issues with your account please contact Support at https://zapier.com/app/get-help.

3. investigating Jul 07, 2026, 09:35 PM UTC

   We’re aware of an issue where some users who try to start a Teams trial from our pricing page are instead placed on a Pro trial, so Teams features may not be available during the trial. Our engineering team is investigating a fix to restore the correct Teams trial signup experience. We will provide the update by 4:15pm PT / 23:15 UTC. If you’re experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

4. monitoring Jul 07, 2026, 10:53 PM UTC

   We've identified and applied a fix for the issue where users signing up for a Teams trial from our pricing page were instead being placed on a Pro trial. New signups should now correctly receive a Teams trial with full access to Teams features. If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

5. resolved Jul 08, 2026, 12:08 AM UTC

   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.

Read the full incident report →

Started Jun 30, 2026, 01:46 AM UTC· resolved Jul 02, 2026, 01:10 PM UTC

1. investigating Jun 30, 2026, 01:46 AM UTC

   We are currently investigating an issue with the Slack "Find Message" action that is preventing it from finding bot messages in Slack channels. What's happening Our team has identified that the Slack Find Message action is failing to find bot messages, while searches for human messages continue to work normally. Customers attempting to search for bot messages are seeing errors like "Nothing could be found for the search" or the step finds the closest matching non-bot message. Current status We've confirmed this issue is reproducible and are actively investigating its root cause. We apologize for any disruption this may cause to your workflows while we investigate this issue.

2. investigating Jun 30, 2026, 02:30 AM UTC

   We’re investigating the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. At this point, we're coordinating with the Slack team to troubleshoot and understand the underlying behavior, and we’ll share updates as we learn more. If you need help with this in the meantime, please contact our support team through this link: https://zapier.com/app/get-help

3. investigating Jun 30, 2026, 04:21 PM UTC

   We’ve confirmed the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. At this point, we’re actively still coordinating with the Slack team to understand the reasons for the change in behaviour, and we’ll share updates as we learn more. If you need help with this in the meantime, please contact our support team through this link: https://zapier.com/app/get-help

4. resolved Jul 02, 2026, 01:10 PM UTC

   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

Read the full incident report →

Started Jun 18, 2026, 09:18 PM UTC· resolved Jun 18, 2026, 11:13 PM UTC

1. investigating Jun 18, 2026, 09:18 PM UTC

   We’re currently experiencing an issue where some Zapier Agents runs may fail or be missed. This may affect: • Zapier Agents • Agent-triggered workflow runs Zapier’s core automation systems are otherwise continuing to process normally. If you need help, contact Support: https://zapier.com/app/get-help

2. resolved Jun 18, 2026, 11:13 PM UTC

   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.

Read the full incident report →

Started Jun 18, 2026, 05:12 PM UTC· resolved Jun 18, 2026, 06:12 PM UTC

1. investigating Jun 18, 2026, 05:12 PM UTC

   We are currently investigating an issue causing delays in the processing of webhook-based triggers. As a result, some Zaps that rely on trigger events may run later than usual. This may affect trigger events across a range of apps. No trigger data is being lost — affected events are delayed, not dropped, and will be processed once the system catches up. Our team is actively investigating and working to restore normal processing times. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

2. monitoring Jun 18, 2026, 05:20 PM UTC

   A fix has been implemented and we are monitoring the results. We increased processing capacity to clear the backlog of delayed webhook-based trigger events, and trigger processing has returned to normal. No trigger data was lost during the incident — affected events were delayed rather than dropped, and the backlog has now cleared. Our team is continuing to monitor processing times closely to ensure they remain stable. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

3. resolved Jun 18, 2026, 06:12 PM UTC

   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.

Read the full incident report →

Started Jun 18, 2026, 02:50 PM UTC· resolved Jun 26, 2026, 04:28 PM UTC

1. investigating Jun 18, 2026, 02:50 PM UTC

   We're received reports of missed leads for Facebook Lead Ads triggers. We're currently working with our Partners at Meta to figure out the root cause and implement a fix as soon as possible. We'll be updating this status page with our progress. Many thanks for your patience! If you have any questions, feel free to reach us at zapier.com/get-help.

2. investigating Jun 18, 2026, 06:21 PM UTC

   We continue to work with our Partners from Meta to identify the root cause and provide next steps. We remain available at zapier.com/get-help if you have any questions or need assistance.

3. identified Jun 19, 2026, 01:42 PM UTC

   We're in active coordination with our partners at Meta, who have identified an issue with their webhook delivery to 3rd party apps. Meta's incident team is engaged and working toward remediation.

4. monitoring Jun 24, 2026, 01:09 PM UTC

   We continue to work in active coordination with Meta, who have implemented a fix to reduce impact to your workflows and resume the proper delivery of leads. Their incident team is proactively applying further optimizations, and monitoring the situation to confirm resolution. If you have any questions or need help, contact us at zapier.com/get-help.

5. resolved Jun 26, 2026, 08:12 AM UTC

   This incident has now been resolved, and all services are operating normally. If you continue to experience any issues, please reach out to our Support team: https://zapier.com/app/get-help

6. resolved Jun 26, 2026, 08:40 AM UTC

   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. If you continue to experience any issues, please reach out to our Support team: https://zapier.com/app/get-help

7. resolved Jun 26, 2026, 04:28 PM UTC

   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

Read the full incident report →

Started Jun 15, 2026, 09:52 PM UTC· resolved Jun 16, 2026, 02:36 AM UTC

1. investigating Jun 15, 2026, 09:52 PM UTC

   We are receiving customer reports that Zap workflows using Facebook Lead Ads or Facebook Pages are returning the following error when Zap runs occur. "An unknown error occurred." Users are also unable to connect to existing or create new app connections, with those connections instantly expiring. We're looking into the issue to identify its root cause.

2. monitoring Jun 15, 2026, 11:02 PM UTC

   Our Engineering team has completed its initial investigation and is now working with Facebook to resolve the issue. Errors have decreased during our investigation, but we will continue to monitor for any spikes until we hear back from the Facebook team. We will provide updates as soon as we have more information.

3. resolved Jun 16, 2026, 02:36 AM UTC

   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.

Read the full incident report →

Started Jun 14, 2026, 06:06 AM UTC· resolved Jun 14, 2026, 09:14 AM UTC

1. investigating Jun 14, 2026, 06:06 AM UTC

   We’re investigating an issue causing intermittent errors when loading Zapier Templates pages "Zapier Templates pages": https://zapier.com/templates, including some template detail/category pages (for example, Lead Management). You may see pages fail to load or display server errors intermittently. Our team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. If you require any assistance, please contact our Support Team: https://zapier.com/app/get-help

2. monitoring Jun 14, 2026, 08:37 AM UTC

   We’re seeing recovery for the issue affecting Zapier template pages "Zapier template pages": https://zapier.com/templates. The templates page should now be accessible again, and we’re continuing to monitor stability. Our team is still investigating and working on preventative measures to reduce the chance of this happening again. We’ll post another update when we have more information or when we’re ready to mark this resolved. If you continue to see errors accessing templates, contact Support: https://zapier.com/app/get-help.

3. resolved Jun 14, 2026, 09:14 AM UTC

   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.

Read the full incident report →

Started Jun 12, 2026, 03:03 AM UTC· resolved Jun 12, 2026, 03:51 AM UTC

1. investigating Jun 12, 2026, 03:03 AM UTC

   We are currently investigating an issue affecting the Templates feature on our platform. Users may experience errors when attempting to load or select templates. Our team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. If you require any assistance, please contact our Support Team: https://zapier.com/app/get-help Thank you for your patience.

2. monitoring Jun 12, 2026, 03:38 AM UTC

   Templates should now be loading normally for users. We’re continuing to monitor and investigate to prevent this from happening again. If you’re still seeing issues, please contact Support: https://zapier.com/app/get-help

3. resolved Jun 12, 2026, 03:51 AM UTC

   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

Read the full incident report →

Started Jun 12, 2026, 02:32 AM UTC· resolved Jun 12, 2026, 02:33 AM UTC

1. identified Jun 12, 2026, 02:32 AM UTC

   Some webhook-triggered Zap runs are experiencing processing delays. Our team is actively investigating the cause and working toward a resolution.

2. resolved Jun 12, 2026, 02:33 AM UTC

   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.

Read the full incident report →

Started Jun 08, 2026, 05:28 PM UTC· resolved Jun 08, 2026, 06:18 PM UTC

1. identified Jun 08, 2026, 05:28 PM UTC

   We identified an issue that caused some Chatbots to fail or time out when customers initialized chats or interacted with embedded chatbots. Some users may have seen a "Forbidden" error. • The affected period was approximately 11:00 PM – 5:30 AM MST on June 8, 2026. • Zap Runs and tasks were not affected. • No data loss is expected. • The issue has since self-resolved. Chatbots metrics are healthy and error rates have returned to normal. We traced the cause to a degradation in our LLM proxy, which led to backend request timeouts and dropped chatbot connections. We are continuing to investigate the scope of customer impact and will post another update soon. If you experienced issues with Chatbots during this window or notice anything still not working, please contact Support: https://zapier.com/app/get-help

2. resolved Jun 08, 2026, 06:18 PM UTC

   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

Read the full incident report →

Started Jun 06, 2026, 12:11 AM UTC· resolved Jun 06, 2026, 12:36 AM UTC

1. investigating Jun 06, 2026, 12:11 AM UTC

   Templates pages are intermittently failing to load in production. Users may see errors when loading the Templates page or individual template pages, and some content (like images) may not display correctly. We’re actively investigating and will share another update when more information is available. Questions? Contact Support: http://zapier.com/app/get-help

2. monitoring Jun 06, 2026, 12:24 AM UTC

   Templates pages are loading normally again after intermittent loading errors. We’re continuing to monitor performance and traffic to ensure the issue does not recur. If you’re still seeing problems, please contact Support: https://zapier.com/app/get-help.

3. resolved Jun 06, 2026, 12:36 AM UTC

   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

Read the full incident report →

Started Jun 05, 2026, 06:14 PM UTC· resolved Jun 05, 2026, 07:41 PM UTC

1. investigating Jun 05, 2026, 06:14 PM UTC

   We have received reports that Zap History export notifications are not being sent when customers are requesting an export of their Zap runs. This means that emails with the download link for those exports are not being sent. Our team is working to identify and resolve the issue as soon as possible. We'll continue to give updates as we make progress.

2. identified Jun 05, 2026, 07:19 PM UTC

   Our Engineering team has identified the root cause of the issue and is working towards resolving it. We'll continue to update as we make progress!

3. resolved Jun 05, 2026, 07:41 PM UTC

   A 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://zapier.com/app/get-help

Read the full incident report →

Started Jun 03, 2026, 01:49 PM UTC· resolved Jun 03, 2026, 04:00 PM UTC

1. identified Jun 03, 2026, 01:49 PM UTC

   We are currently experiencing issues with our Shopify app due to an upstream outage affecting Shopify's services. Multiple Shopify systems are impacted, including Admin, Checkout, Storefront, and Point of Sale. Users may be unable to complete actions that rely on Shopify integrations at this time. We are monitoring the situation closely and will provide updates as more information becomes available. For real-time updates on Shopify's service status, please visit their official status page: https://www.shopifystatus.com We apologize for any disruption this may cause. Once Shopify services are restored, we will work to ensure all affected workflows resume normal operation. Thank you for your patience.

2. monitoring Jun 03, 2026, 03:34 PM UTC

   Shopify Service Update We're pleased to report that Shopify's services have recovered and are operating normally. We've confirmed that our Shopify app is now functioning as expected, and zap triggers and actions are executing successfully. What you can do If you had zaps that failed during the outage window, you can manually replay those failed runs to push the data through your workflows. To do this: 1. Open the affected zap in your Zap History 2. Locate the failed run(s) from the outage period 3. Select the run and choose to replay it Your zap will then attempt to complete the action with the current data. Next steps We're continuing to monitor both Shopify's status and our own systems to ensure full stability. If you experience any further issues with your Shopify integrations, please don't hesitate to reach out to our support team. Thank you for your patience during this incident.

3. resolved Jun 03, 2026, 04:00 PM UTC

   Shopify 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, and multiple other services. This caused failures in both Zap triggers and Zap actions that rely on Shopify integrations. What we did Once Shopify's services were restored, we automatically replayed all impacted Zap runs to ensure your workflows could complete successfully. Any remaining failed runs will be handled by our automatic replay system. No further action is required from you. We've completed our investigation and confirmed all systems are stable. If you experience any further issues with your Shopify integrations, please don't hesitate to reach out to our support team. Thank you for your patience during this incident.

Read the full incident report →

Started Jun 02, 2026, 10:33 PM UTC· resolved Jun 02, 2026, 11:16 PM UTC

1. investigating Jun 02, 2026, 10:33 PM UTC

   We are currently investigating an issue with Code by Zapier that is resulting in error messages when those steps are running: “Lambda was unable to configure access to your environment variables, because you have reached the grant limit of your KMS key or execution role”. We are working on resolving this as soon as possible, and will update this Status page as soon as possible. If you have any questions, please reach out to our support team — https://zapier.com/app/get-help Thank you for your patience!

2. monitoring Jun 02, 2026, 11:01 PM UTC

   A fix has been implemented and we are now monitoring the results. Code by Zapier steps that were failing with the environment variable error should now be running normally again. We are continuing to watch closely to confirm full recovery, and any tasks that were affected during the disruption are being replayed. We’ll post a final update once we’ve confirmed the issue is fully resolved. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

3. resolved Jun 02, 2026, 11:16 PM UTC

   This 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 our support team: https://zapier.com/app/get-help Thanks again for your patience while we working on resolving that.

Read the full incident report →

Started Jun 02, 2026, 03:54 PM UTC· resolved Jun 02, 2026, 05:26 PM UTC

1. investigating Jun 02, 2026, 03:54 PM UTC

   We are currently investigating an issue affecting the ability of Code by Zapier steps to run. Starting at approximately 11:00am EST, some Code by Zapier steps began encountering errors, including CodeStorageExceededException OR ResourceConflictException This is affecting new Code by Zapier steps, and some existing steps as well. We will provide updates as we make progress on resolving this issue. Thank you for your patience.

2. investigating Jun 02, 2026, 04:51 PM UTC

   We're continuing to investigate reports of errors affecting Code by Zapier steps, including “CodeStorageExceededException” and “ResourceConflictException.” Our engineering team remains actively engaged in identifying the cause of the issue. While we do not have any new information to share at this time, we will provide further updates as our investigation progresses. If you have any questions, please reach out to our support team — https://zapier.com/app/get-help Thank you for your patience and understanding.

3. monitoring Jun 02, 2026, 05:20 PM UTC

   We have pushed out a fix for this Code by Zapier error, and are monitoring the results to ensure that it is working as intended, and fully clearing up those errors. Once we have been able to confirm that this issue is officially resolved, we will update this Status to reflect that. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you again for your patience and understanding.

4. resolved Jun 02, 2026, 05:26 PM UTC

   We 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. If you are running into this error, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we resolved that.

Read the full incident report →

Started May 22, 2026, 06:34 PM UTC· resolved May 22, 2026, 07:16 PM UTC

1. investigating May 22, 2026, 06:34 PM UTC

   Sidekick users are experiencing an issue with getting logged out, and running into session errors. After the users then log back in, they are no longer able to see and access workspace content and chats. We are currently investigating the cause of this issue, and will update here once we have more information.

Read the full incident report →

Started May 20, 2026, 11:57 PM UTC· resolved May 21, 2026, 03:05 AM UTC

1. investigating May 20, 2026, 11:57 PM UTC

   We have identified delays between Zap execution and when runs become visible in Zap History. Importantly, Zap executions themselves are not failing or delayed — this issue only impacts the visibility of Zap History data in the UI. Our team is actively investigating the issue and we will continue to provide updates as soon as more information becomes available.

2. resolved May 21, 2026, 03:05 AM UTC

   This 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 worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help

Read the full incident report →

Started May 20, 2026, 05:16 PM UTC· resolved May 20, 2026, 06:58 PM UTC

1. investigating May 20, 2026, 05:16 PM UTC

   Starting around 1:55 p.m. UTC, Code by Zapier steps have started failing with the error: "No response from child process" Our team is actively investigating and has engaged the owning engineering team.

2. monitoring May 20, 2026, 05:38 PM UTC

   What happened: Between approximately 10:00 AM EDT and 1:28 PM EDT today, some Team plan Zaps with Python Code Steps failed with this error: "Error: No response from child process" Who was affected: Team plan customers using Python Code Steps only. Other plan types (Enterprise, Pro, Free) and other Code Step languages were not affected. What we did: We disabled a recent change that routed Team plan Code Steps through a new system. Error rates dropped significantly after this change, and we have not seen new occurrences in the last several minutes. What’s next: We are monitoring for stability and will post a final update shortly. If you need help, contact Support: https://zapier.com/app/get-help

3. resolved May 20, 2026, 06:58 PM UTC

   The 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. After our team disabled this change, error rates dropped significantly and we have not seen new occurrences since this change. Impact The incident lasted approximately 3 hours and 28 minutes (14:00–17:28 UTC). All affected tasks have been replayed and are now executing successfully. No data was lost, and no action is needed on your side for these runs directly. We apologize for the disruption and appreciate your patience while we resolved this issue. If you do see any further issues with any code steps on your account, please reach out to our team at https://zapier.com/app/get-help

Read the full incident report →

Started May 20, 2026, 12:43 PM UTC· resolved May 20, 2026, 05:00 PM UTC

1. investigating May 20, 2026, 12:43 PM UTC

   We are currently experiencing intermittent authentication and connection issues affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations. Users may see authentication failures or connection errors when attempting to use Zaps with these LinkedIn integrations. These issues began around 1:50am EDT on May 20th and are impacting a subset of our users. LinkedIn's platform is experiencing widespread API issues, resulting in elevated error rates (primarily 401 authentication failures and 500 server errors). This has been confirmed on LinkedIn's API status page. We are actively monitoring the situation and working with LinkedIn to track their recovery progress. We apologize for any disruption this may cause to your workflows. We'll continue to monitor this closely and will update you as the situation develops.

2. monitoring May 20, 2026, 04:10 PM UTC

   We’re seeing recovery in LinkedIn and LinkedIn Ads integrations after an upstream LinkedIn API incident that caused intermittent authentication and API errors (401/500/503). Our internal error rates have returned to normal levels and we’ve replayed a small set of impacted tasks. We’ll continue monitoring closely and will share another update if anything changes. If you’re still seeing issues, please retry your connection or task and contact Support "contact Support ": https://zapier.com/app/get-help with a link to the affected Zap.

3. resolved May 20, 2026, 05:00 PM UTC

   The 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 integrations should be working normally again. If you still see errors, retry your connection or Zap task. If you need help, contact Support: https://zapier.com/app/get-help

Read the full incident report →