Hi , I run workflows ,which are workable before, not work. Some of them run and keep loading. For some workflow, it not work even I run the executive button (no response at all). i have redeploy and my version is 2.3.6
im not sure but it looks like you’ve redeployed and your workflow version is 2.3.6, which is the latest stable release. can you confirm if you’re running the exact same configuration as shown in the images and if there’s anything specific that’s changed?
also, since some workflows are loading indefinitely without error, i’m curious to know more about those specific cases - do they share any common nodes or configurations?
The config is the same; it review the log in Railway (self host) and I notice there is an error. Any idea how to fix it?
Your error is that it’s not executing because of a 545 error, and it cannot read the properties of the execution data, so its aborting the run. This is a bug with your n8n instance. I’m not exactly sure how to fix it, but it is within the n8n instance files.
It can be if the railway instance is running in queue mode or a misconfiguration between the n8n instance and the worker nodes. I would change some settings and keep testing.
Hi @Ken_Chan1,
Are you able to run any other workflows, or is the issue only with the Chat & AI Agent workflow?
Do you have any custom nodes installed?
Do you remember changing/installing anything recently that might be related?
What’s your current setup look like on Railway?
-
Thx for question; recently, I am not able to run all my workflow even I create some simple workflow like form submission. It does not work. I can’t recall any specific update before.
-
I have 2 communities nodes installed (@havebeenfitz/n8n-nodes-mcp and n8n-nodes-serpapi).
-
My Railway setup is a Queue Mode configuration consisting of four interconnected services:
-
Primary: Running
n8nio/n8nvia Docker. -
Worker: A dedicated worker node is online.
-
Postgres: Used as the main database with a persistent volume.
-
Redis: Used for the execution queue with a persistent volume.
Key Variables:
-
N8N_RUNNERS_ENABLED: true -
EXECUTIONS_PROCESS: main -
EXECUTIONS_TIMEOUT: 1800 (Max 3600) -
All Redis connection variables (Queue Bull) are mapped to the Redis service
Attached list of variable name for reference.
Okay,
so to make things easier and see where the problem is, can you uninstall the community nodes?
after that make sure you’re on the latest version of n8n, deploy and then try again..
I have uninstalled the community nodes; deploy and try again. The error still remain unchanged.
Error log message in Railway seems a bit different.
Log from Railway:
“Problem with execution 552: Error: Cannot read properties of undefined (reading ‘execute’). Aborting.
Error: Cannot read properties of undefined (reading ‘execute’) (execution 552)
at NodeTypes.getByNameAndVersion (/usr/local/lib/node_modules/n8n/src/node-types.ts:57:32)
at new Workflow (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/workflow.ts:98:30)
at JobProcessor.processJob (/usr/local/lib/node_modules/n8n/src/scaling/job-processor.ts:112:20)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Queue.<anonymous> (/usr/local/lib/node_modules/n8n/src/scaling/scaling.service.ts:102:5)
Enqueued execution 552 (job 552)
Execution 552 (job 552) failed
TypeError: Cannot read properties of undefined (reading ‘execute’)
at shouldAssignExecuteMethod (/usr/local/lib/node_modules/n8n/src/utils.ts:88:13)“
