Hi,
If you create by mistake a webhook loop : for example you modify the same record in the update webhook…
The update creates a stack of webhook future calls which can be huge…
It should be possible to purge this stack no?
Regards
Hi @gdoumenc,
We don’t necessarily have built-in infinite loop prevention like that, but eventually the CMA rate limits should kick in (60 requests / 3 seconds). Though I suppose if each request takes long enough, it might never reach that limit and just keep going…
I don’t know that we could automatically detect or prevent this… there are sometimes legitimate reasons to update the same record that sent the webhook, e.g. a webhook script that adds some computed metadata after a human editor makes a manual change. Does that sound reasonable, or do you think there is a way to prevent this without causing side effects?
If you notice a loop like this happening, you should be able to just disable the webhook in the project settings. New requests will stop, and eventually the existing stack of requests will deplete itself… at some point.
Hopefully this isn’t still happening for you…?
By customer request, we are closing this request. (Turns out it was a loop happening on their side)