Problem stopping execution: Maximum call stack size exceeded

Questions
1

Hello,

Sometimes when an execution is running too long, and I try to stop it, I get the message: “Maximum call stack size exceeded”. Does anybody know what the problem is?

image
image710×204 11.9 KB

Information on your n8n setup

  • n8n version:1.25
  • Database (default: SQLite):postgress
  • n8n EXECUTIONS_PROCESS setting (default: own, main):?
  • Running n8n via (Docker, npm, n8n cloud, desktop app):Docker
  • Operating system:linux

Kind regards,

Jos

2

Maximum call stack size exceeded is a very generic error that comes from JavaScript when either there is too much recursion, or when a function is receiving too many arguments.

during the execution do you have any node outputting more than 10,000 items?

Can you please share a workflow where you can reproduce this? That might really help fix this quicker.

2 Likes
3

Hello,

I don’t have an example that would be of much use to you.

The (very heavy) flow contains a loop that iterates more than 2000 times. So I guess, the error doesn’t have so much to do with stopping the execution, but rather with the excessive number of iterations.

Regards,

Jos

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.