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

Ignore error in Zap

  • October 6, 2020
  • 2 replies
  • 1242 views
C

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

Upon investigation, we have a step where we are looking up Slack users by email. If a user isn’t found an error is thrown, and I don’t see any way to gracefully handle this to prevent an error. If a user isn’t found it should just stop the zap but not cause an error. How do I configure this? 

 

 

Thank you!

Best answer by codygordon

Don’t see a way to close this, but these aren’t actually errors – we had some other real errors happening!

View original
    Did this topic help you find an answer to your question?
    This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

    2 replies

    C
    • codygordonBeginner
    • Author
    • Beginner
    • 1 reply
    • Answer
    • October 6, 2020

    Don’t see a way to close this, but these aren’t actually errors – we had some other real errors happening!

    W
    • Waylan
    • New
    • 1 reply
    • October 21, 2020

    @codygordon  How did you go with this? I’m having a similar issue.

    Terms & Conditions