Hi n8n team and community,
I made a critical mistake and accidentally exhausted my entire monthly execution limit overnight. I’m hoping someone can help.
What happened:
I was building a product indexer workflow with an Orchestrator + Worker pattern. The Schedule Trigger was supposed to run every 30 seconds, but I accidentally set it to 5 seconds.
The workflow ran overnight and executed 10,000+ times before I noticed this morning - consuming my entire monthly allocation in less than 12 hours.
The impact:
My team relies on several critical n8n workflows for our e-commerce business:
Automatic inventory sync
Product import automation
Order processing
All of these are now blocked until next month, which seriously impacts our daily operations.
What I’ve done:
Immediately deactivated the problematic workflow
Identified and documented the misconfiguration
My request:
Is there any possibility to get a one-time exception or partial reset of our execution limit? I understand this was my mistake, but it was an honest configuration error, not intentional overuse.
Our instance ID: 75e2d2264d6b7140d50e2b2320be4f6d13d105fcccd06aee35d73a3959213ac7
Thank you for any help or guidance you can provide.
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
).