Zapier

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.

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

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.

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

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

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

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.

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.

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!

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.

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.

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.

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.

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.

Our Engineering team is currently monitoring reports indicating that Enterprise users with a high number of app restrictions (over 100) are unable to modify or manage custom actions. Affected users will see the following error when viewing custom actions. We couldn't determine whether this app is restricted. Please try again in a moment. We'll continue to keep our customers informed as we identify the root cause and resolve the issue.