Execution quota exhausted during Telegram bot testing

Questions
1

Hello!

I’m a new n8n Cloud user and currently building/testing my Telegram bot workflow.

During development and testing I accidentally exhausted my execution quota, and now my Telegram Trigger no longer works because executions are blocked.

Would it be possible to get a one-time execution reset for my workspace?

Thank you very much!

3

Hi @dimkost97, welcome!
N8N Cloud has a one-time courtesy reset for these kinds of failures please consider dropping a mail at support@n8n.io or any of the channels listed here Where To Ask N8n Questions And Get Fast Answers | Qixazow, and there, explain what has happened exactly and then provide your instance details such as username and ID, and they will be able to reset it for you.

4

Welcome to n8n, @dimkost97! Anshul’s advice is spot-on - reach out to support and they should be able to sort that reset for you.

For future testing with Telegram bots specifically, a few tips to avoid burning through your quota:

  • Use a test Telegram bot (create a separate bot via BotFather just for dev) rather than your production one - this way you won’t accidentally send yourself a flood of messages during iteration
  • Disable the Telegram Trigger and test with Manual Trigger + sample data while you’re building out the workflow logic. Only switch to the live trigger once the core logic is solid
  • Set a low polling interval during testing, or switch the trigger to webhook mode, so it only fires when you deliberately send a message rather than polling continuously
  • Pin the “Executions” sidebar open while testing so you can see the count going up and catch it early

Hope you get that reset quickly and the bot comes together well!