Single http request hitting rate limit

[sentry]

Describe the problem/error/question

When calling a http endpoint, I am receiving an error back from the API stating that I made too many calls, but my flow should only be sending one call per execution.

What is the error message (if any)?

“684 requests, exceeds limit of 600 in 300 seconds. Try again in 167 seconds, or contact [email protected]”

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version:
  0.230.3
• Database (default: SQLite):
  Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
  Docker
• Operating system:
  Linux (Synology)

[BramKn]

Hi @sentry

Welcome to the community!

Are there 600+ items going into the node making the request? That would cause it to execute so many times.

[sentry]

Hey Bram, thanks for the reply. There’s not - I have one webhook hitting with a single JSON payload, I show 1 item going into the HTTP request:

[sentry]

Here is the full error:

{"status":"rejected","reason":{"message":"503 - \"{\\\"type\\\":\\\"Error\\\",\\\"error\\\":\\\"Throttled\\\",\\\"message\\\":\\\"684 requests, exceeds limit of 600 in 300 seconds. Try again in 167 seconds, or contact [email protected]\\\"}\"","name":"Error","stack":"Error: 503 - \"{\\\"type\\\":\\\"Error\\\",\\\"error\\\":\\\"Throttled\\\",\\\"message\\\":\\\"684 requests, exceeds limit of 600 in 300 seconds. Try again in 167 seconds, or contact [email protected]\\\"}\"\n at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:238:9)\n at RedirectableRequest.emit (node:events:525:35)\n at RedirectableRequest.emit (node:domain:489:12)\n at RedirectableRequest._processResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:356:10)\n at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:62:10)\n at Object.onceWrapper (node:events:628:26)\n at ClientRequest.emit (node:events:525:35)\n at ClientRequest.emit (node:domain:489:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:693:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)\n at TLSSocket.socketOnData (node:_http_client:534:22)\n at TLSSocket.emit (node:events:513:28)\n at TLSSocket.emit (node:domain:489:12)\n at addChunk (node:internal/streams/readable:315:12)\n at readableAddChunk (node:internal/streams/readable:289:9)\n at TLSSocket.Readable.push (node:internal/streams/readable:228:10)\n at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)"}}

[BramKn]

hmm, strange.
When you execute it does it simply add one to the nr of requests?
And does it ever work?
Seems to be some other requests that are causing it.

[sentry]

Interestingly enough, this tested OK for a few weeks up until this morning when I moved to production. I’ve reached out to LiquidPlanner to see if there’s some issue with my API key. I wasn’t making any other API calls elsewhere at the time, at least that I was aware of.

Do you know if there’s a way to find the raw outbound payload that was being sent?

Thanks,
Brandon

[BramKn]

Something must be happening with that api for it to complain about the number of requests.
Doesnt seem like this is an n8n issue, unless you are having this flow run 600+ times in a short period. Or other flows that talk with the same api.

[sentry]

I believe you are correct. I couldnt find the offending service but I rolled my API keys and the errors stopped. I will monitor for now. Thanks!