Zapier Outage History

Zapier's Templates pages experienced intermittent loading failures for 27 minutes, causing users to encounter errors when accessing template pages and preventing some content like images from displaying correctly. The issue affected the main Templates page and individual template pages across Zapier's website. The service was restored to normal operation and the team continued monitoring to prevent recurrence.

Zapier experienced an issue where Zap History export notification emails containing download links were not being sent to users who requested exports of their Zap runs. The engineering team identified the root cause and worked to resolve the problem. The incident lasted 1.5 hours and was classified as minor impact.

Zapier's Shopify integration experienced a 2.2-hour disruption due to an upstream outage affecting multiple Shopify systems including Admin, Checkout, Storefront, and Point of Sale. Users were unable to complete actions that relied on Shopify integrations during this period. The service was restored once Shopify's systems recovered, with users advised to manually replay any failed zap runs from the outage window.

Zapier's Code by Zapier service experienced a 44-minute outage caused by Lambda errors related to KMS key grant limits, preventing code steps from executing properly. Users encountered error messages stating "Lambda was unable to configure access to your environment variables, because you have reached the grant limit of your KMS key or execution role" when their automation workflows tried to run code steps. Zapier implemented a fix and began replaying affected tasks, with the service returning to normal operation.

Zapier experienced a 1.5-hour incident where Code by Zapier steps encountered errors including CodeStorageExceededException and ResourceConflictException, affecting both new and existing code steps. Users reported being unable to publish Zap updates, reply to Zaps, or run their automations during the outage. The engineering team deployed a fix and monitored the resolution to ensure the errors were fully cleared.

Zapier Sidekick users experienced unexpected logouts and session errors that prevented them from accessing workspace content and chats after logging back in. The issue affected the website components and lasted for 27 minutes. The incident was classified as minor and was under investigation during the reported timeframe.

Zapier experienced delays in displaying Zap execution data in the Zap History UI, though the actual Zap executions continued to run normally without failures or delays. The issue affected users' ability to view their automation run history in the interface for 3.2 hours. The team investigated and resolved the visibility problem while maintaining normal Zap functionality throughout the incident.

Between approximately 10:00 AM EDT and 1:28 PM EDT, Team plan customers using Python Code Steps experienced failures with "No response from child process" errors, while other plan types and code languages were unaffected. The issue was resolved by disabling a recent change that routed Team plan Code Steps through a new system, which significantly reduced error rates within 1.7 hours.

Zapier experienced intermittent authentication and connection issues with LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations for 4.3 hours starting at 1:50am EDT on May 20th. The issues were caused by widespread API problems on LinkedIn's platform, resulting in 401 authentication failures and 500 server errors that affected a subset of users' Zaps. The incident was resolved after LinkedIn's API recovered, with Zapier's error rates returning to normal and impacted tasks being replayed.

Zapier experienced an issue where Enterprise users with over 100 app restrictions were unable to modify or manage custom actions, receiving an error message stating "We couldn't determine whether this app is restricted. Please try again in a moment." The incident was classified as minor and was resolved after 49 minutes of monitoring by the Engineering team.