Skip to main content

I have a zap triggered by a notification from a third party app. I’m using the catch hook function in the webhook trigger. 

 

The zap was triggered thousands of times by the single inbound notification. I’m trying to figure out if its a one time bug or if there is an issue. There is only a single outbound webhook from the source application. But Zapier triggered multiple times, effectively using up all our zap actions, flooding the downstream apps and forcing it to hold. There is no looping functions or anything that would trigger additional triggers. As far as i can tell its an issue with zapier, but don’t know how to otherwise confirm it. I don’t want to turn it on again to troubleshoot for fear of triggering the repetition again. Zapier support won’t support it.

 

I also don’t see an option to add flood protection for this zap so it doesn’t get stuck in the process again.

 

Any way to figure out from the logs where the issue is?

Hi @justino 

You can open a ticket with Zapier Support for help troubleshooting: https://zapier.com/app/get-help

 

In your Zap Runs history, check the timestamps of the steps.

Perhaps an infinite loop got created.

For reference, Zapier Status page that indicates ongoing/recent incidents: https://status.zapier.com/#incidents-list

 



Per Zap settings for flood protection:
https://help.zapier.com/hc/en-us/articles/14230420160269-Choose-your-Zaps-flood-protection-limit