About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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

Never Replay Advanced Setting Not Working for Webhooks

  • 5 March 2024
  • 4 replies
  • 27 views
tpretori
Userlevel 2
Badge +1

https://www.loom.com/share/90f5c786e1354b248a68d9de9e4cd6f2?sid=08b24937-b25c-4c98-b88e-f1be07e85bf6

 

It appears the zap is resending "failed" webhooks 10minutes after the initial send, which it should not be doing since "Never Replay" is enabled, which is causing the 3rd party automation which logs to the Google sheet to run twice since it gets triggered from the webhook sending from Zapier

 

Is this a bug on Zapier’s end or is there anything I can do on the configuration side to stop this?

icon

Best answer by tpretori 8 March 2024, 00:15

View original
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
Userlevel 7
Badge +14

Hi @tpretori 

Try using the new feature available for custom error handling: https://help.zapier.com/hc/en-us/articles/22495436062605-Set-up-custom-error-handling

 

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
tpretori
Userlevel 2
Badge +1

Thanks Troy, unfortunately I have not been invited to that closed beta so I can’t use error handling.

 

Do you or does anyone else have any other suggestions?

Troy Tessalone
Userlevel 7
Badge +14

@tpretori 

Try adding Paths and create your own custom error handling after the Zap step that can error.

2 Paths.

  • Path A Filter condition if a value is returned
  • Path B Filter condition if a value is not returned
⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
tpretori
Userlevel 2
Badge +1

What I have found out after checking our logs is actually related to the way our delay process is designed.  In the back end of things, Delay does a very similar process than a replay would.
 
After the delay step hits the release time, the process goes over any 'unplayed' steps in the Zap until it hits the delay stage and then continues with the rest of the workflow.
 
Because our process does not recognize the timeout as an actual error, it defaults to try sending your POST again as it was never technically labeled as an 'error' as such. Since the HTTP call has no status, it tries to process again. 

 

This was the feedback from Zapier support.

 

Based on this feedback I moved the delay and subsequent steps into a sub-zap, which worked to solve the issue.

 

I suggested this to support and this was their thoughts on why it would work:

 

It's possible that creating a sub-zap with a delay and subsequent steps might help in this situation. The idea behind this is to isolate the delay and subsequent steps from the main zap. This way, if there is a timeout on the webhook, the sub-zap will not be triggered again.
 
This method essentially makes your main zap and sub-zap work together, but the sub-zap will only run when it's triggered by the main zap. If the webhook times out, it shouldn't trigger the sub-zap again.

 

 

 

Terms & Conditions