N8n node response size limits?

[robjennings]

Hello,

Does n8n Nodes have any kind of limitation in terms of json sizes to be returned?

Sometimes when I use either the MISP or Elasticsearch Nodes, and select the “Return All” switch, I don’t get all documents. The list of documents to be returned are roughly 10k, so I believe this is the problem.

Can you confirm?

Kind regards,
Rob

Information on your n8n setup

• n8n version:
• Database you’re using: SQLite
• Running n8n with the execution process: own
• Running n8n via: Docker

[MutedJam]

Hi @robjennings, you have most likely encountered what I think is a bug:

Wanted to get all the documents inside a index in elastic search

Hm, this seems unexpected me tbh @LENINDALLAS. From looking at the code it seems the ReturnAll option simply means no limit parameter is set and Elastic’s default is used (which appears to be 10). Unfortunately, I don’t understand Elasticsearch well enough to fix this myself (it should require specifying a sorting parameter and then use the search_after parameter for pagination, but there might be other implications). So I’ll add this to our internal bug tracker for a closer lok.

I have added this to our bug tracker last week but do not have any feedback yet I am afraid.

In general, there is no global limit in n8n, but sometimes pagination does no longer work as expected (for example because an API might have changed without us noticing) or some API rate limit might kick in before pagination is complete.

You should always be able to use the HTTP Request node to directly send requests to more or less any REST API in such cases.