Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Zap was stopped due to high error ratio - how to check for error?

  • September 17, 2021
  • 4 replies
  • 219 views
K

We are having a major issue where our zap is turning itself off with this message: Zap was stopped due to high error ratio

How can I prevent Zap from stopping?
If this is not possible, what should I check to determine the cause of the error?

Best answer by SamB

Following up here as I spotted @K.A also reached out to our Support team about this. They found that the errors couldn’t be viewed in the Zap History as they occurred back in June. We can can only guarantee a maximum of one month of Zap run data in your Zap history - Zap History storage. As there has been no further instances of this, it appears that the issue has since been resolved. :)

If a Zap repeatedly runs into errors then as a safety precaution we’ll automatically turn it off. The best way to prevent this from happening is to update your email notification settings to ensure you receive errors as they happen (Manage notifications when errors occur in Zaps), review any errors in the Zap History, then troubleshoot and fix them so that they no longer occur.

You can find out more about troubleshooting Zap errors in this guide: Troubleshoot errors in Zapier

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • September 17, 2021

Hi @K.A 

What apps are you using in your Zap?

What Zap step is causing the error?

Check your Zap Runs history for the DATA IN/OUT for each Zap step to help you troubleshoot: https://zapier.com/app/history/

⚡ Troy Tessalone - AutomationAce.com | Platinum Zapier Solution Partner | #1 Zapier Community Contributor
K
  • K.ABeginner
  • Author
  • Beginner
  • September 17, 2021

Hi @Troy Tessalone 

Thanks for the reply.

 

>What apps are you using in your Zap?

  • New or Updated Spreadsheet Row in Google Sheets
  • Create Record in Salesforce
  • Update Spreadsheet Row in Google Sheets
  • Create Spreadsheet Row in Google Sheets
  • Lookup Spreadsheet Row in Google Sheets
  • Send Channel Message in Slack

 

>What Zap step is causing the error?

I can't confirm that because it's not logged.

 

 

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • September 17, 2021

@K.A

Might be best to open a ticket with Zapier Support for further help: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Platinum Zapier Solution Partner | #1 Zapier Community Contributor
SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • Answer
  • November 17, 2021

Following up here as I spotted @K.A also reached out to our Support team about this. They found that the errors couldn’t be viewed in the Zap History as they occurred back in June. We can can only guarantee a maximum of one month of Zap run data in your Zap history - Zap History storage. As there has been no further instances of this, it appears that the issue has since been resolved. :)

If a Zap repeatedly runs into errors then as a safety precaution we’ll automatically turn it off. The best way to prevent this from happening is to update your email notification settings to ensure you receive errors as they happen (Manage notifications when errors occur in Zaps), review any errors in the Zap History, then troubleshoot and fix them so that they no longer occur.

You can find out more about troubleshooting Zap errors in this guide: Troubleshoot errors in Zapier

Terms & ConditionsAccessibility statement