Because of third party service bug got all executions eaten out in a minute

Describe the problem/error/question

Hi, because of the incorrect execution from 3rd party webhook we have suddenly maxed out the executions within minute since it sent a 5000 rows of data. Could be these executions refunded or somehow bough more? Thanks

Hey @Illia, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@Jon_James, @libstrom, @dev_scaleupally - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

@Illia

Please reach out to help@n8n.io for a one time execution limit reset if you have exhausted this months quota

Hi @Illia Welcome!
A Webhook trigger counts one execution for every inbound request that activates it, whatever the payload carries, so 5000 separate calls burn 5000 executions while the same 5000 rows arriving in one request would have cost one. If that third party can be set to post in batches, that is the change that stops this repeating.

If you are on Cloud, buying extra executions and how the tiers differ is covered here:

This @Sasidhar-Sunkesula provided information is incorrect.
If a webhook starts your flow 5000 times you cannot fix that in your workflow. The webhook already triggered so it counts…

Changing ENV settings is not possible on a cloud instance, also the settings you mention make no sense for this.

Please make sure your AI answers the question correctly or do not post it at all.
If the person asking a question starts following your suggestions they will just waste their time…

It is not allowed to post AI responses, please just leave the forum or make sure to follow the rules.