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.

I am developing an update our integration and am hitting issues when testing error conditions when a subscribe call comes through. 

I have currently set up the integration point in our app to throw a 400 error when calling “subscribe” for a trigger for testing.

What I am seeing is that when adding the Zap in the Zapier interface, it shows the Zap as being enabled, but behind the scenes a 400 error is thrown preventing call success.  Zapier notes the 400 error in the event log, so I definitely know that Zapier is receiving it. The Zap shows as enabled until you refresh the page which then updates to show the Zap as not enabled.. 

Basically it appears that Zapier doesn’t handle error conditions on subscribe. 

Has anyone else encountered this?  If so can you shed light on whether it is a bug in the Zapier interface or should I just not expect Zapier to handle this well?

Hi @Sean Gay 

Seems like your topic should be posted in the Developer Zone category: https://community.zapier.com/p/developer-zone

Reply


Terms & Conditions