Bug maximum call stack size exceeded has reoccurred

[N0Name]

The “Maximum call stack size exceeded” error was fixed in version 1.61:

• Release [email protected] · n8n-io/n8n · GitHub
• fix(MySQL Node): Fix “Maximum call stack size exceeded” error when handling a large number of rows by netroy · Pull Request #10965 · n8n-io/n8n · GitHub
  But the bug has reoccurred in versions 1.65 and above. Could you please work on fixing this issue again?

Information on your n8n setup

• n8n version: 1.74.3
• **Database (default: SQLite):Postgres
• **Running n8n via (Docker, npm, n8n cloud, desktop app):docker
• **Operating system:AWS Linux AMI

[Jon]

Hey @N0Name

Are you using the mysql node? It would be handy to have the workflow and the full stack trace so we can take a look.

[N0Name]

After running node ‘Api test’, it seems that the task generates the following error:

Queue errored
Error: Missing lock for job 10431 failed
at Object.finishedErrors (/usr/local/lib/node_modules/n8n/node_modules/bull/lib/scripts.js:225:16)
at Job.moveToFailed (/usr/local/lib/node_modules/n8n/node_modules/bull/lib/job.js:342:19)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
Worker errored while running execution 43300 (job 10431)
Cannot read properties of undefined (reading ‘node’) (execution 43300)

This ‘Workflow’ worked correctly in 1.61 but since my n8n updated (1.70) it no longer works.

[N0Name]

Hi Jon,
Any problem to fix it ? The problem is different or has nothing to do with it ?