# Avoid a endless loop when using webhooks that trigger update

**URL:** <https://community.nocodb.com/t/avoid-a-endless-loop-when-using-webhooks-that-trigger-update/729>\
**Category:** Uncategorized\
**Created:** [December 10, 2022, 12:52pm UTC](https://community.nocodb.com/t/avoid-a-endless-loop-when-using-webhooks-that-trigger-update/729 "2022-12-10T12:52:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![systemaddict](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@systemaddict](https://community.nocodb.com/u/systemaddict)\
**Post date:** [December 10, 2022, 12:52pm UTC](https://community.nocodb.com/t/avoid-a-endless-loop-when-using-webhooks-that-trigger-update/729/1 "2022-12-10T12:52:38Z")

</div>

Hi

I’ve got a table that triggers a webhook on update. The code (that the webhook activates) eventually writes a status back to the table (Succesfull update). But this in turn triggers a new update and so on spinning the system in to an endless loop.

I could probably work with some filters to avoid this but I don’t think it would be safe enough (just one error and the endless loop would re-appear). It would be nice if you could somehow disable webhooks when calling the update method from the API perhaps?