Slowness is concerning a lot "Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed"

Questions
1

Describe the problem/error/question

What is the error message (if any)?

Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Folks need you assistance, this is a major blocker

3

If it is a major blocker and want an answer you should really give us more information. As you are just giving us an error and “slowness” we cannot really help with just that information. :wink:

4

My bad, here is the additional info

I have setup the K8s based N8N instancee, we’re with 10-15 workflows.

we’ve noticed the drastic slowness while workflow execution. During the log observation we’ve noticed these

“”“”“”
2025-04-10T09:02:30.480Z | debug | Executing Tools Agent {“file”:“execute.js”,“function”:“toolsAgentExecute”}
2025-04-10T09:02:30.482Z | debug | Supply data for embeddings {“file”:“EmbeddingsAzureOpenAi.node.js”,“function”:“supplyData”}
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMStart: TypeError: fetch failed
2025-04-10T09:03:06.071Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
Error in handler N8nLlmTracing, handleLLMEnd: TypeError: fetch failed
2025-04-10T09:03:19.717Z | debug | Running node “API discovery agent” finished successfully {“node”:“API discovery agent”,“workflowId”:“5iVKKUUNbC7fpZcJ”,“file”:“LoggerProxy.js”,“function”:“exports.debug”}

“”“”“”

continuous log lines until workflow executed. Although its a simple workflow still consuming more time to execute.

Information on your n8n setup

  • n8n version: 1.83.2
  • Database (default: SQLite): RDS
  • n8n EXECUTIONS_PROCESS setting (default: own, main): NA
  • Running n8n via (Docker, npm, n8n cloud, desktop app): K8s (Conatiner based)
  • Operating system: K8s Linux
5

Seems like an issue with how this workflow is created. Can you share the workflow as well?

6

Thanks for quick turn around

can you assist me how can i share the workflow

image
image2570×1302 330 KB

Note: I’m using the Community Edition, the same workflow running much faster in the macbooks or local laptops

7

Can some one pls assist on this

8

Folks pls assist

9

Knocking off

10

think its related to Issue with LLMChain and AgentNodes. Too slow and error - #5 by c_Gor

11

Any solution for it ? pls

12

can someone share what is the solution on this? i am having the same issue. using 1.93.0 with npm community edition. i can see the response return from the LLM but logfile having N8nLlmTracing error and it is extremely slow when running in webhook

13

Hi, in a post referenced above there is an advise to remove N8nLlmTracing, how exactly to do that?

“just remove N8nLlmTracing from packages/@n8n/nodes-langchain/nodes/llms/LMChatOpenAi/LmChatOpenAi.node.ts”

14

i am seeing that the latest n8n version resolved this issue.