N8n-ai stuck at thinkng

Questions
1

Not sure why, but n8n-ai is stuck at the thinking stage. I have tried reloading the browser, and then it works. But for the second request, it gets stuck again. Any idea what might be the issue?

Also how can I contact n8n support for a query like this?

2

could be a cache or token timeout issue. try opening it in an incognito tab to see if the browser cache is the problem, or check if theres a delay between requests thats causing the token to expire. also check the browser console for errors when it gets stuck — might give you a clue what n8n support needs to know

3

Hi @hefty , welcome!

Are you referring to the built-in AI assistant in the n8n editor (the AI helper that builds workflows), or an AI Agent node in one of your workflows?

Could you share your n8n version and whether you’re on Cloud or self-hosted? That’ll help narrow it down.

1 Like
4

Welcome to the community @hefty :tada:

This is likely a network or browser issue as it works fine here. Btw when did the error of been stuck at thinking start?

1 Like
5

@JohnHalex I have been noticing the error from yesterday.

@houda_ben yes, I am talking about the built-in ai assisstant by n8n that helps with creating workflows. I am using 2.15.0 version. And I am using cloud version of n8n.

6

Adding to the great suggestions above — if this is the n8n AI assistant (the built-in AI that generates workflows), a common cause is a WebSocket connection timeout. The AI builder uses a persistent WebSocket connection, and if your network drops briefly or there’s a proxy/firewall in between, it can hang silently.

Fix to try:

  1. Check browser console (F12 → Console) for any WebSocket error messages
  2. If on a corporate network, check if WebSocket connections are allowed
  3. Try with a different browser (Chromium-based browsers tend to work best)
  4. If self-hosted: check if there’s a reverse proxy (nginx/Caddy) with a read timeout — set it to at least 120 seconds

If it’s an AI Agent node stuck in a loop: that’s usually the LLM going into infinite tool calls. Adding maxIterations in the node settings can help.

1 Like
7

Screenshot 2026-04-09 at 15.33.41
Screenshot 2026-04-09 at 15.33.411920×1576 171 KB

Unfortunately still not working. I have tried in incognito mode and also in Chromium browsers.

8

Hi @hefty Welcome!
For support you can read this:

Also for your question that it works but it does not makes me think that it is mainly a problem related to the browser you use, for now lets switch a browser from maybe Chrome to Zen, also just in case try using a different AI provider maybe is causing some problem. (Also try to access n8n from a different device that will confirm the issue)

9

welcome to the n8n community @hefty
I couldn’t find an exact GitHub issue for this, so I think it would be worth opening one.

Since you’re on n8n Cloud 2.15.0 and already tested the usual browser-side fixes, this looks specific enough to report, especially with the Maximum call stack size exceeded console error.

If possible, I’d also include a minimal reproduction: the shortest prompt sequence that works once and then consistently gets the assistant stuck. That usually makes it much easier for the team to verify and debug.

1 Like