Unrecognized node type after infinite loading on custom node

Questions
1

Describe the problem/error/question

I am using a self-hosted n8n instance on version 2.9.4. I used version 2.7.2 before this, which had the same issue. I use 4 external runners. Whenever I execute my workflow, which contains my custom node, most of the time it will not run the node but get stuck on trying to start the node execution. So the loading bar on the execute workflow button is loading, but nothing is happening. When I stop the execution, I get an error which should not be possible saying that the node type of the custom node is not recognized when it does get installed correctly on startup (error shown below). I’ve been trying a lot and I can’t figure out what causes this issue. This doesn’t seem to happen when I run the instance locally (from my vsc terminal with n8n-cli) and without runners (I presume the default n8n debug instance doesn’t use runners).

The code used for this node is from this repository. I edited it to include OAuth1 support, but I disabled it whilst testing this. It has no effect on this issue.

As shown in the image here, it shows that it’s loading, but it doesn’t do anything. This is after a few minutes of it loading. This process normally takes a few seconds to a maximum of 20 seconds.

image
image1367Ă—817 24.5 KB

After I press the stop execution button, this is what it shows along with the error down below.

image
image606Ă—259 7.95 KB

What is the error message (if any)?

image
image2238Ă—1275 409 KB

This error is from worker number 1, but the same error is displayed across all workers whenever it picks it up.

2026-04-07T14:00:04.360Z | error | Worker errored while running execution 127 (job 127) {“scopes”:[“scaling”],“error”:{“name”:“Error”,“message”:“Unrecognized node type: n8n-nodes-test-random.netSuiteRest”,“stack”:“Error: Unrecognized node type: n8n-nodes-test-random.netSuiteRest
at LoadNodesAndCredentials.getNode (/usr/local/lib/node_modules/n8n/src/load-nodes-and-credentials.ts:596:10)
at NodeTypes.getByNameAndVersion (/usr/local/lib/node_modules/n8n/src/node-types.ts:82:45)
at new Workflow (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/workflow.ts:95:30)
at JobProcessor.processJob (/usr/local/lib/node_modules/n8n/src/scaling/job-processor.ts:130:20)
at processTicksAndRejections (node:internal/process/task_queues:103:5)
at Queue. (/usr/local/lib/node_modules/n8n/src/scaling/scaling.service.ts:130:5)”},“executionId”:“127”,“jobId”:“127”,“file”:“scaling.service.js”,“function”:“reportJobProcessingError”}
2026-04-07T14:00:04.360Z | error | Unrecognized node type: n8n-nodes-test-random.netSuiteRest (execution 127) {“file”:“error-reporter.js”,“function”:“defaultReport”}

Please share your workflow

Share the output returned by the last node

There is none when this problem happens.

Information on your n8n setup

  • n8n version: 2.9.4
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Debian 6.1.159-1
2

Hi @BerkieBb i have seen this problem, majorly when using workers you have to install your CUSTOM NODE into all the WORKERs so that they understand what you want them to process. Basically install your custom node in your docker images in all the instances, Do this:

FROM docker.n8n.io/n8nio/n8n:2.9.4
# Copy your compiled custom node into the custom directory
COPY dist/nodes/ /home/node/.n8n/custom/

and after installing restart everything, for a safety measure consider enabling this N8N_REINSTALL_MISSING_PACKAGES=true so that in case if package is missing it would install that.

3 Likes
3

Wow, that fixed it instantly, thank you so much! I’ve been struggling with this for weeks.

1 Like