Custom node has issues in n8n cloud after update. Takes hours to work

Questions
1

Describe the problem/error/question

Good morning everyone, I hope you’re all doing well. I’m facing some issues that I suspect might be related to the build process of my custom node. The error is as follows: After making some changes to the code by adding new features, after updating via “Community Nodes,” errors appear, particularly in the areas where I added the new functionalities.

What puzzles me the most is that this only happens in the n8n cloud version. On two different computers running n8n locally via Docker, when I install the node via Community Nodes, they work perfectly without any issues. The local version doesn’t show any errors of this kind. And the strangest part: after trying everything and nothing working, I decided to wait a while. Almost without fail, the day after making changes and publishing to npm, the functionalities that were previously erroring start working perfectly.

For example, yesterday I was getting a “route not found /” error, even though the route was correct. I tested it with curl, and it was accessible. It also worked perfectly locally. So, yeah :/. Anyway, it’s weird, and I strongly suspect it might be related to the build process—perhaps I misunderstood something and did it in a way that compromises it. Thanks in advance for your attention.

In the beginning, when I updated it, it would work perfectly. Could it be some kind of cache or something similar that’s persisting?

What is the error message (if any)?

I’m running into different problems with my custom node after an update in n8n cloud. For example, the last issue was about it not finding a route, even though the route was correct. For example, today it’s working perfectly, but I think there’s still a problem. It can’t be right that every time I update the node, I have to wait a day for it to work.

Please share your workflow

Share the output returned by the last node

From NI Node
Error code
404
Full message
Request failed with status code 404
Error data
{ “message”: “The route / could not be found.” }
Other info
Item Index
0
Run Index
0
Node type
n8n-nodes-notificacoes-inteligentes.NI
Node version
1 (Latest)
n8n version
1.110.1 (Self Hosted)
Time
25/09/2025, 12:11:46
Stack trace
NodeApiError: The resource you are requesting could not be found at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1365:9) at processTicksAndRejections (node:internal/process/task_queues:105:5) at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1737:11) at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:531:20) at RoutingNode.makeRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:725:19) at async Promise.allSettled (index 0) at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:234:29) at ExecuteContext.versionedNodeType.execute (/usr/local/lib/node_modules/n8n/src/node-types.ts:60:18) at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1254:8) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1428:11) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1760:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2337:11
Other info
Item Index
0
Run Index
0
Node type
n8n-nodes-notificacoes-inteligentes.NI
Node version
1 (Latest)
n8n version
1.110.1 (Self Hosted)
Time
25/09/2025, 12:11:46
Stack trace
NodeApiError: The resource you are requesting could not be found at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1365:9) at processTicksAndRejections (node:internal/process/task_queues:105:5) at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1737:11) at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:531:20) at RoutingNode.makeRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:725:19) at async Promise.allSettled (index 0) at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/routing-node.ts:234:29) at ExecuteContext.versionedNodeType.execute (/usr/local/lib/node_modules/n8n/src/node-types.ts:60:18) at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1254:8) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1428:11) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1760:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_5aee33ef851c7de341eb325c6a25e0ff/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2337:11

Information on your n8n setup

2

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