n8n - 💡(How to fix) Fix "error : The connection was aborted, perhaps the server is offline" [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28669Fetched 2026-04-20 12:15:10
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0

Error Message

Describe the problem/error/question

I'm experiencing an intermittent timeout on an AI Agent node that calls the Anthropic API to generate long-form SEO articles. The error occurs randomly — not on every execution, with the same node and similar input sizes. When it fails, the execution appears to hit a connection timeout mid-generation rather than the model simply being slow, since identical executions succeed shortly after.

What is the error message (if any)?

Node error: Full error: No output is returned when the error occurs — the node fails with the timeout above and no partial content is produced.

  • The Anthropic API is not down when the error occurs — other executions succeed shortly after
RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

I'm experiencing an intermittent timeout on an AI Agent node that calls the Anthropic API to generate long-form SEO articles. The error occurs randomly — not on every execution, with the same node and similar input sizes. When it fails, the execution appears to hit a connection timeout mid-generation rather than the model simply being slow, since identical executions succeed shortly after.

What is the error message (if any)?

Node error:

Problem in node 'Agent Claude - Rédaction' The connection was aborted, perhaps the server is offline

Full error:

timeout of 300000ms exceeded

Node involved: AI Agent (LangChain) using the native Anthropic credential, model claude-opus-4-6, called inside a loop processing items one by one.

Share the output returned by the last node

No output is returned when the error occurs — the node fails with the timeout above and no partial content is produced.

Debug info

core

  • n8nVersion: 2.16.1
  • platform: cloud
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • license: pro

client

  • userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36
  • Generated at: 2026-04-20T07:51:49.410Z

Additional context

  • The Anthropic API is not down when the error occurs — other executions succeed shortly after
  • The issue is not consistently tied to article length or input size (same brief can succeed or fail)
  • Is there a known connection keep-alive limitation for long-running LLM calls on N8N Cloud Pro? Is there a way to configure retry behavior or extend the HTTP connection timeout on the AI Agent node?

extent analysis

TL;DR

Configure the AI Agent node to retry failed requests or extend the HTTP connection timeout to mitigate intermittent timeouts when calling the Anthropic API.

Guidance

  • Investigate the Anthropic API documentation for any known limitations on connection keep-alive for long-running LLM calls.
  • Check the N8N Cloud Pro documentation for configuration options to extend the HTTP connection timeout on the AI Agent node.
  • Consider implementing a retry mechanism for failed requests to handle intermittent timeouts.
  • Verify that the issue is not related to network connectivity or server overload by monitoring the node's performance and error rates.

Example

No code snippet is provided as the issue is related to configuration and API interaction.

Notes

The issue may be specific to the N8N Cloud Pro environment and the Anthropic API, so it's essential to consult the relevant documentation and support resources for more information.

Recommendation

Apply a workaround by configuring the AI Agent node to retry failed requests or extending the HTTP connection timeout, as upgrading to a fixed version is not implied in the issue. This approach can help mitigate the intermittent timeouts and improve the overall reliability of the node.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix "error : The connection was aborted, perhaps the server is offline" [1 participants]