Is there a way to add a cooldown period to a workflow, so as to prevent frequent Webhook triggering? Like only allow one successful execution every 10 minutes.
n8n version: 1.1.1
Database (default: SQLite): Postgres
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: Debian
Hi @Bonislaw
I was wondering whether it was possible to wait for let’s say 1 minute, if the same webhook is triggered more than once, and only then trigger a workflow.
I had the issue this morning that a webhook was fired four times (it should’ve only triggered once), and then based on this executed a workflow four times instead of just once. This way I could filter out and account for a malfunctioning of this webhook in the future (it is not intended to fire more than once per day.
Thanks!
1 Like
Thanks for providing this idea. This does seem like a tricky question since this solution introduces many extra factors.
2 Likes
system
November 8, 2023, 5:38am
4
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
This is a little tricky with webhooks - can you take a look at this thread and see if maybe this has a solution for you?