Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix 3 years of operations credits in 3 days

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

  • error: all

Code Example

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Hi n8n Support Team,

I'm reaching out regarding an issue that has resulted in a significant and unintended consumption of my operation quota over the past few days.

Here is what happened:

  1. I built a workflow for a job interview assignment, it was set to poll every minute.
  2. Before leaving for a long weekend, I believed I had paused it. It was not paused.
  3. I received notifications that I had reached my operation limit. I upgraded my plan to continue working.
  4. A few minutes ago, I received another alert indicating I had again exhausted my operation quota, despite all my scenarios being in a paused state at that point.

This second depletion is what I cannot explain. My workflows were paused. No executions should have run. Something appears to have continued consuming operations in the background without any active workflow on my end.

I have been using n8n with my clients for several years. This week alone, I have lost the equivalent of years of accumulated operations in 3 days — partly due to my own mistake on the first incident, but the second depletion while workflows were paused is not something I can account for.

My requests are:

  1. Please investigate what caused the second operation drain while my workflows were paused.
  2. Based on your findings, please consider a full or partial reset/refund of the operations consumed , in particular those consumed during the paused state.

Debug info for reference:

  • n8n version: 2.18.4
  • Platform: Docker (cloud)
  • License: Enterprise (sandbox)
  • Execution mode: Regular
  • Generated: 2026-05-09T23:08:12Z

I'm happy to share workflow exports, execution logs, or any additional context that would help your investigation.

Thank you for looking into this.

Best regards

Please share your workflow/screenshots/recording

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.18.4
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-09T23:08:12.961Z

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING