Status: Resolved 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

Delays between Zap execution

Status: Resolved 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 Affected components
 <ul>
 <li>Instant Triggers (Operational)</li>
<li>Searches & Writes (Operational)</li>
<li>Polling Triggers (Operational)</li>
 </ul>

Code Steps failing with "No response from child process" across Zaps/APIs

Status: Resolved 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

LinkedIn Integrations— authentication and connection errors

Status: Resolved The 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 issues, contact Support: https://zapier.com/app/get-help

Thank you for your patience.

Customer with a large number of app restrictions cannot manage custom actions.

Status: Complete Successfully completed maintenance. Polling-based triggers have resumed. Missed polls should be picked up. Affected components
 <ul>
 <li>Polling Triggers (Operational)</li>
 </ul>

Maintenance: Scheduled: Infrastructure Maintenance

Status: Resolved Between approximately 1:20 AM UTC and 10:38 AM UTC on May 13, 2026, Zaps using Facebook Lead Ads experienced failures due to an upstream issue with Meta’s Facebook Lead Ads API.
During this time, Facebook Lead Ads Zaps were unable to process new leads. Some Zaps may have been automatically turned off due to repeated errors.
Meta has resolved the issue on their end, and error rates have returned to normal. Your Zaps should now be functioning as expected, and new leads from Facebook will resume flowing through normally.
Zaps that were automatically turned off have been re-enabled, and failed runs have been replayed.
If you’re still experiencing issues, contact Support: https://zapier.com/app/get-help

Facebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"

Status: Complete We have successfully completed the scheduled maintenance. All systems are operational. Affected components
 <ul>
 <li>Login (Operational)</li>
 </ul>

Maintenance: Scheduled platform upgrade

Status: Resolved Our Engineering team has monitored our backend for any spikes in errors after the fix was released, and we're happy to see that we're at normal operation and no longer seeing errors.

As such, the incident is now considered resolved. Please reach out to our Support team if you continue to see issues or have questions about the incident.

Errors when creating or reconnecting app connections

Status: Resolved The issue has been resolved, and all systems are back to normal.

High Latency is impacting hook ingestion

Status: Resolved The issue causing incorrect “High Error Ratio” notifications has been resolved.

Impact
 Some users received an email titled “High Error Ratio” indicating their Zap would be switched off. In certain cases, this did not reflect actual Zap performance, and some Zaps may have been paused incorrectly as a result.

Resolution
 We implemented a fix and confirmed that notifications and Zap status are now behaving as expected.

If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Zap error notifications

Status: Resolved Our team has confirmed that since 21:14 UTC all customers logging into Zapier via Google SSO can do so successfully. If you are still running into any issues, please contact our support team for assistance: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Login (Operational)</li>
 </ul>

Google SSO Login Failures

Status: Resolved The issue causing 522 timeout errors with the Klaviyo app integration has been resolved. This was related to an upstream service disruption on Klaviyo's side: https://status.klaviyo.com/incidents/yyh7s59brj67

Zaps using Klaviyo should now be functioning as expected. No data loss occurred — any Zap runs that failed during the incident can be replayed from Zap History.

If you are still experiencing issues with your Klaviyo integration, please contact Support: https://zapier.com/app/get-help

Thank you for your patience.

Errors related to Klaviyo app integration

Status: Resolved We’ve resolved an issue where some users could see a “Session initialization failed” error when creating new app connections. The issue was caused by an unintended staged rollout configuration and was mitigated by rolling back the rollout.

Existing Zaps and workflows were not impacted. If you saw a failed connection attempt during the incident window, please retry creating the connection now.

If you’re still experiencing issues creating new app connections, please contact Zapier Support.

Session initialization failed error when trying to connect apps

Status: Resolved We've implemented an update so webhooks sent with a Content-Type header that specified a non-UTF-8 character set will trigger your Zaps.

Incoming webhooks — some requests not processed (encoding in Content-Type)

Status: Complete The scheduled maintenance on Zapier Tables has been successfully completed. All services are now operating normally.

Thank you for your patience. If you continue to experience any issues, please don’t hesitate to reach out to support. Affected components
 <ul>
 <li>Tables (Operational)</li>
 </ul>

Maintenance: Zapier Tables maintenance

Status: Resolved No additional customer reports have been received during the monitoring period. The incident is ready to be closed. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

INC-908: Firecrawl outage

Status: Resolved The performance issues that caused delays and timeouts on Zapier.com "Zapier.com": http://Zapier.com have now been resolved. Our systems have remained stable, and signing in, loading account information, and running Zaps should behave normally.
During the incident, some customers may have seen slower responses, failed actions, or delayed trigger processing while we reduced load and shipped the fix. Everything should now be caught up; if you still see anything unexpected, try running your Zap again.

If you need help with a specific Zap or account, contact our Support team: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
<li>Login (Operational)</li>
<li>Support (Operational)</li>
 </ul>

Service delays and timeouts across Zapier.com

Status: Resolved We can confirm that the Admin Center is now loading as expected, and the issue is now resolved. If you're still unable to load the page, you may need to reload the page and/or clear your browser's cookies and cache.

If you're experiencing any issues with this was not resolved by clearing browser cache and cookies, please reach out to our support team here: https://zapier.com/app/get-help

Users are unable to access Admin Center.

Status: Resolved The issue preventing ownership transfer in Teams and Enterprise accounts has been resolved. Account ownership transfers can now be self-served by following this guide: https://help.zapier.com/hc/en-us/articles/17946190203789-How-to-transfer-ownership-of-your-Team-or-Enterprise-account

If you're experiencing any issues with this, please do reach out to our support team here: https://zapier.com/app/get-help

"Unable to verify identity. Please try again." Error when transferring ownership between Team members.

Status: Resolved The issue affecting invoice access and downloads has been resolved. Service was fully restored at 18:30 UTC on April 27, 2026.

At 17:20 UTC an outage from the Databricks App caused invoices to fail to load or download from the Billing and Invoices Page. Databricks released a fix for their outage and invoices are functioning as normal. If you attempted to view or download any invoices during this time, you can retry that action now.

We apologize for the inconvenience this caused and appreciate your patience while the issue was resolved.

If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

500 error when viewing upcoming invoices

Status: Complete The maintenace is now complete. Affected components
 <ul>
 <li>Developer Platform (Operational)</li>
 </ul>

Status: Resolved The issue causing some AI by Zapier steps to fail with a 500 error when adding a knowledge source has been resolved.

If you were affected by this issue, your Zaps with AI by Zapier steps using knowledge sources will now work again. To restore functionality:


1. Open the affected Zap and navigate to the AI by Zapier step
2. Before deleting the step, we recommend copying and saving your prompt to avoid losing any work.
3. Delete the step
4. Re-add the AI by Zapier step
5. Copy your previous prompt into the new step
6. Re-upload your knowledge sources


Once you've completed these steps, your Zap will be ready to use.

If you are experiencing this issue, you can connect with our support team here: https://zapier.com/app/get-help.

AI by Zapier action Fails with 500 error when a Knowlledge source is added

Status: Resolved The issue affecting chatbot users has been resolved. Chat completion features are now functioning normally, and users should no longer encounter error messages when interacting with chatbots.

Chatbot

Status: Resolved We have successfully resolved the chatbot availability issue that affected some of our users. Our engineering team identified and resolved the underlying authentication issue.

All chatbot services are now operating normally. You should now be able to view and manage your chatbots in the dashboard and use them externally without any issues. We have monitored and verified that the service is working properly.

We apologize for any disruption this may have caused. If you experience any further issues accessing your chatbots, please contact our support team: https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Chatbots (Operational)</li>
 </ul>

Chatbots failing to load

Status: Resolved We confirm that the fix deployed has resolved the issue with Agents and Canvas, and both are functioning correctly. All Agent workflow executions that were stuck on 'In Progress' status during this incident have been replayed.

If you are experiencing any issues with Zapier Agents or Canvas, please contact our support team through this link: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Canvas (Operational)</li>
<li>Agents (Operational)</li>
 </ul>

agents.zapier.com is down

Status: Resolved This incident is fully resolved. Customers can now create Chatbots and Forms as usual. 

Many thanks for your patience, and feel free to reach out to our support team if you have any questions at: zapier.com/get-help. Affected components
 <ul>
 <li>Forms (Operational)</li>
<li>Chatbots (Operational)</li>
 </ul>

Creation of new chatbots and forms results in an error

Status: Resolved We have resolved the issue with web-scraping tools not working throughout tools like Agents, Chatbot knowledge sources, and Web Parser.

For any questions, or if you're still seeing failures with web-scraping tools in Zapier, please contact: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Chatbots (Operational)</li>
<li>Agents (Operational)</li>
 </ul>

Web-scraped sources cannot be added to Chatbots, and Agents not returning informatio

Status: Resolved We have been able to get this issue resolved.

Users should now be able to successfully download their Zap Run History export files.

If you are running into any other issues, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Zap Run History Export Download Links Returning Errors

Status: Resolved The connectivity issue which affected Zapier Agents during a 15 minute window is fully resolved. Agent executions are back to normal, and connectivity remains stable.

If you have any questions, please reach out to our support team at: zapier.com/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Temporary Agent run executions errors during a 15-minute window

Status: Resolved The issue causing 404 errors when editing and deleting Zap templates has been resolved.

Users attempting to edit templates were encountering 404 errors due to a routing misconfiguration introduced during an ATC (Application Traffic Control) rollout, which changed the default ATC origin from the monolith to the marketing site. This broke routing for the /zap-templates path, causing edit actions to fail.

The fix was deployed by completing the ATC routing correction to production. Once the rollout completed, edit functionality was restored. A remaining cosmetic bug — where the UI incorrectly indicates a template deletion failed despite the deletion succeeding — has been identified as a separate, no-impact bug and does not affect actual data.

No data was lost as a result of this incident.

If you're still experiencing issues, please contact Support by clicking above or visit: https://zapier.com/app/get-help

Thank you for your patience.

404 Errors while editing templates

Status: Resolved We have successfully resolved the intermittent delays affecting Slack-triggered Zaps that began around Friday, April 11th. Our engineering team identified and deployed a fix, and Slack triggers are now operating as expected.

If you continue to experience any delays with your Slack-triggered Zaps or have any questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help

We appreciate your patience while we worked through this issue.

Slack Triggerred Zaps: Delays in triggering

Status: Resolved Copilot "Ask" mode is up and running again and and can be utilized for all accounts.

Earlier today the "Ask" mode was malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users attempted to build Zaps.

If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help

Thank you for your patience. Affected components
 <ul>
 <li>Copilot (Operational)</li>
 </ul>

Copilots "Ask" mode is not working correctly

Status: Resolved We've identified and resolved the soft timeout limit errors that were impacting Code by Zapier and Custom Action steps. This issue was affecting the execution and processing of these steps across multiple Zaps. All affected runs have been automatically replayed.

If you experienced any issues or need additional support, please feel free to reach out at https://zapier.com/app/get-help

Errors related to Custom Actions and Code by Zapier steps

Status: Resolved This issue has been resolved, and agent executions are operating normally.

Between April 6, 2026, at 22:12 UTC and 22:47 UTC, a dependency that powers Agents became unavailable due to internal load test traffic.

Agents triggered during this window may have failed to execute and will not be automatically retried. Agents that run from a Zap have been replayed and succeeded as well.

If an agent run failed during this window, re-run the agent (or trigger it again via its normal trigger mechanism). New executions should now succeed.

We apologize for the disruption. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Intermittent agent execution failures

Status: Resolved The incident affecting some custom action steps has been resolved.

Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions.

Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.

Delayed or failed custom action requests

Status: Resolved We've identified and resolved the root cause of the functions outage.

The issue has been resolved and systems are operating normally.

The team will continue to monitor performance and ensure full recovery across all impacted users. Affected components
 <ul>
 <li>Functions (Operational)</li>
 </ul>

Functions not executing

Status: Complete The maintenance is now complete. Affected components
 <ul>
 <li>Tables (Operational)</li>
 </ul>

Status: Resolved resolved Affected components
 <ul>
 <li>Functions (Operational)</li>
 </ul>

Update PostgreSQL from version 14 to 17.

Status: Resolved Our team has resolved the issue, and connections can now be established again.

Facebook Lead Ads and Microsoft apps are returning 'Cache key will cause errors if used with memcached' errors when creating new connections

Status: Resolved This is now resolved. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Zapier Agents - Webhook triggers showing a placeholder URL

Status: Resolved We’ve resolved an issue where adding certain knowledge sources in Zapier Agents could get stuck on a loading spinner. A fix has been deployed to production and verified.

If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Zapier Agents - Adding a knowledge source modal is stuck on a loading spinner

Status: Resolved We’ve resolved the issue causing intermittent Internal Server Errors (HTTP 500) for some Enterprise customers when editing Zaps that use app approvals.

Our teams implemented a fix and confirmed recovery. If you continue to experience issues editing affected Zaps, please contact support. https://zapier.com/app/get-help Affected components
 <ul>
 <li>Zap Editor (Operational)</li>
 </ul>

Internal Server Errors (HTTP 500) affecting Zaps

Status: Resolved We’ve resolved the issue related to Zaps that were paused during a prior authentication incident.

Some Zaps were automatically paused as a protective measure during an earlier incident "an earlier incident": https://status.zapier.com/incidents/01KMZFA6V1H9WP71FD7XZ8MP4A and did not automatically resume afterward. We investigated and confirmed the scope, and provided guidance directly to affected customers on how to review and restore any impacted Zaps.

If you believe you may have been impacted, please review any paused Zaps and re-enable them as appropriate.

And as always, Our support team is available if you have questions or need help getting workflows running again. If this is the case, or if you have any other questions please let us know at https://zapier.com/app/get-help

Zaps Paused due Prior Connection Failure with Google Services

Status: Resolved TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently resolved now and everything is functional.
All systems are back to normal

Database Upgrade

Status: Resolved We have successfully completed the recovery process for the intermittent task failures that occurred between March 24-26, 2026. Our team replayed all affected tasks, which have been successful with no data loss.

**What Happened**
Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed for customers using Zaps that depend on our developercli service.

**Resolution**
We fixed the underlying issue causing this failure and completed a full replay of all impacted tasks. No action is needed on your side if affected — tasks have been automatically recovered and are now running normally.

Thank you for your patience while we worked through this issue. If you do have any other questions or see any issues, please reach out to our Support team at zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components
 <ul>
 <li>Zap History (Operational)</li>
 </ul>

Intermittent failures across tasks due to exhausted db connections for developercli

Status: Resolved Earlier, a script error unintentionally detached saved payment methods for some active customers. This caused increased payment errors and prevented some customers from completing checkout, renewing subscriptions, upgrading plans, or paying invoices.

We worked with Stripe to reattach impacted customers’ payment methods in bulk, including a final batch for any remaining affected accounts. Payment processing has resumed and our monitoring indicates payment error rates and invoice processing are back to normal.

If you’re still having trouble making a payment, please contact Support: https://zapier.com/app/get-help

Payment failures for some customers

Status: Resolved We’ve completed our review of the publicly reported LiteLLM package issue. Zapier was not affected.

Our review confirmed that the LiteLLM versions used in our environments were not among the publicly reported impacted versions, and we found no evidence of unauthorised access or impact on customer data, Zapier systems, or services.

We will continue to monitor for any new information and will share updates if anything changes.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help.

Monitoring a publicly reported LiteLLM package issue

Status: Resolved We’ve deployed a fix for the issue that prevented some users from adding or removing tools on Zapier MCP servers, and we’ve confirmed the issue is resolved.

We apologize for the disruption and appreciate your patience as we got this resolved.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

MCP Servers: Issues adding/removing tools

Status: Resolved Resolved - We have confirmed that the issue causing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and during new connection setup has been fully resolved. If you run into any issues, please reach out to us here: https://zapier.com/app/get-help Affected components
 <ul>
 <li>Website (Operational)</li>
 </ul>

OAuth Authorization Page Is Blank

Status: Resolved This issue has now been resolved, and all Zap runs should now be appearing correctly in the Zap history without delay.

We apologize for the disruption and appreciate your patience as we got this resolved.

If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Delay in Zap History displaying Zap Runs

Status: Resolved We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations.

A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations.

All impacts have been mitigated, and authentication error rates have returned to baseline.

If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap "Transfer existing data using a Zap": https://zapier.com/help/manage/history/transfer-existing-data-using-a-zap.

For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help. Affected components
 <ul>
 <li>Agents (Operational)</li>
 </ul>

Connection Failure with Google Services

Status: Resolved The Zap History and Task Usage pages are now loading normally again. During this incident, you may have experienced slow load times, intermittent errors, or missing data on the Zap History and Task Usage pages. Zap executions were not affected and continued to run as expected throughout.

This issue is now considered resolved, and we are continuing to monitor to ensure stability.

If you're still seeing delays or errors on these pages, we recommend clearing your browser's cache and cookies and logging back into Zapier. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.

Delay in loading Zap History and Task Usage

Status: Resolved The checkout page payment and tax modals are now functioning normally again. During this incident, you may have been unable to add or update payment or tax information during checkout.

If you still have trouble updating payment or tax details, you can update your payment method from the billing settings page and then return to checkout.

We apologize for the disruption and appreciate your patience as we got this resolved. If you do see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Checkout page not rendering properly

Status: Resolved We're seeing error levels back to a normal level with no spikes over the last 20 minutes. As such, this issue is now considered resolved.

If you still see the error messages, we recommend clearing Copilot chat by selecting the Settings icon at the top of the Copilot chat window. If that does not work, clear your browser's cookies and cache and then log back into Zapier.

For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help

Copilot intermittently not responding in the Editor

Status: Resolved Our Engineering team has decided to close this incident, as the root cause appears to be Claude's handling of MCP tool calls with Cowork. We have notified the Anthropic team of the issue and will continue working with their Support and Engineering teams to help resolve it.

If you're still running into issues or have questions, we recommend reaching out to Anthropic support by using this Help Center guide: https://support.claude.com/en/articles/9015913-how-to-get-support Affected components
 <ul>
 <li>MCP (Operational)</li>
 </ul>

Degraded Performance for Zapier MCP in Claude CoWork

Status: Resolved Thank you for your patience as we worked to resolve the issue.

We're no longer seeing elevated error rates when customers create app connections, and we can confirm that customers can create new app connections without issue.

This issue is now considered resolved, but feel free to reach out to our Support team if you have questions: https://zapier.com/app/get-help

Users are not able to create new app connections using OAuth flow

Status: Resolved This issue is now resolved.

Zaps that using Notion as a trigger should now be receiving all webhooks and triggering properly.

If you are still running into into issues, please reach out to Zapier Support: https://zapier.com/get-help

Zaps using notion triggers stopped triggering

Status: Resolved Our team has restored full functionality and verified system performance is stable. Since there's full functionality, the incident is considered closed.

Affected customers have been contacted but no further action is necessary.

If you have any other questions, please feel free to reach out to our support team at https://zapier.com/app/get-help Affected components
 <ul>
 <li>Searches & Writes (Operational)</li>
<li>Polling Triggers (Operational)</li>
 </ul>

Some app integrations experiencing delayed triggers sporadically

Status: Resolved This issue is now resolved, and the Task Usage Page should now be loading correctly for all users.

If you are running into any other issues, please reach back out to Zapier Support: https://zapier.com/app/get-help

Task Usage Page Currently Unavailable

Status: Resolved Between approximately 10:00PM UTC on Feb 23 and 3:20 AM UTC on February 24, we saw errors being returned from the Transcribe cation in AI by Zapier. The team were able to identify and roll-back the change causing this issue and the issue should now be resolved.

If you run into any unexpected errors, please feel free to reach out to us at: https://zapier.com/app/get-help

Is Zapier down?

Zapier status is UP

Lastest published events

Delays between Zap execution

Code Steps failing with "No response from child process" across Zaps/APIs

LinkedIn Integrations— authentication and connection errors

Zapier Services, Components and Regions

Recent Zapier events

Delays between Zap execution

Code Steps failing with "No response from child process" across Zaps/APIs

LinkedIn Integrations— authentication and connection errors

Customer with a large number of app restrictions cannot manage custom actions.

Maintenance: Scheduled: Infrastructure Maintenance

Facebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"

Get your FREE account now,
5 monitors included!

Is Zapier down?

Zapier status is UP

Lastest published events

Delays between Zap execution

Code Steps failing with "No response from child process" across Zaps/APIs

LinkedIn Integrations— authentication and connection errors

Zapier Services, Components and Regions

Recent Zapier events

Delays between Zap execution

Code Steps failing with "No response from child process" across Zaps/APIs

LinkedIn Integrations— authentication and connection errors

Customer with a large number of app restrictions cannot manage custom actions.

Maintenance: Scheduled: Infrastructure Maintenance

Facebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!