Accidental Exhaustion of Executions

Questions
1

Need help.

@Jan I saw that you were able to help other members in the past.

My teammates and I have accidentally exhausted our executions at our client.

We misconfigured a scheduled run at it ran every 10 minutes over the past three days and ran through our executions (as it executes other workflows)

We are getting ready to go live with an n8n powered marketing and Shopify publishing system. If we could get some help to refresh our executions so that we can test and be ready for the Aug 1st deployment to production that would be a godsend.

I apologize for the error on our end and greatly appreciate your help!

2

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

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@Jon_James, @darrell_tw - 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.

3

@occ-acoodledoo

Please reach out to help@n8n.io for a one time execution count reset

4

Hi @occ-acoodledoo Welcome!
Quota resets are handled by n8n’s team directly, not from the forum. Email help@n8n.io from your account email with your workspace URL, mention it was an accidental schedule misconfiguration and that you have a client go-live on Aug 1st, and ask for a one-time reset.
See this:

The sub-workflow calls weren’t what drained it, only the top-level execution counts when a workflow calls another one. The 10-minute Schedule Trigger counted once per fire on its own, regardless of outcome. Manual runs from the editor don’t count against the quota at all, so you can keep building and testing the Shopify publishing flow while you wait on the reset.
If you’re sizing the plan before production, this covers the quotas per tier and buying extra executions: