Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix [Bug] Continuous Workflow Loading & Server Connection Issues — WebSocket Disconnections Since April 16, 2026 [2 comments, 3 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#28603•Fetched 2026-04-18 05:57:18
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
0
Author
richardng1505richardng1505
Participants
KArmbrusterKArmbrustern8n-assistant[bot]n8n-assistant[bot]richardng1505richardng1505
Timeline (top)
commented ×2subscribed ×2labeled ×1mentioned ×1

Persistent workflow loading failures and intermittent server connection losses since April 16, 2026. The issue affects workflow editor responsiveness and causes repeated disconnections.

Root Cause

Persistent workflow loading failures and intermittent server connection losses since April 16, 2026. The issue affects workflow editor responsiveness and causes repeated disconnections.

RAW_BUFFERClick to expand / collapse

Bug Report

Summary

Persistent workflow loading failures and intermittent server connection losses since April 16, 2026. The issue affects workflow editor responsiveness and causes repeated disconnections.

Environment Details

FieldValue
Platformn8n Cloud
Issue Start DateApril 16, 2026 (~2:00 PM ICT)
FrequencyContinuous throughout the day
SeverityHigh — blocks production workflows

Steps to Reproduce

  1. Login to app.n8n.cloud
  2. Open workflow editor for any workflow
  3. Observe continuous loading spinner
  4. Watch for "Connection lost" messages appearing repeatedly
  5. Note automatic logout/session invalidation after short periods

Expected Behavior

  • Workflows load within 1-2 seconds
  • WebSocket connection remains stable
  • Sessions persist across normal use

Actual Behavior

  • Workflow editor shows continuous loading (never fully renders)
  • "Connection lost" popups appear every few minutes
  • API response times degraded (TTFB ~1s, expected <200ms)
  • Automatic session invalidation forcing constant re-login
  • Multiple workflow executions fail or timeout

Network Diagnostics

ping app.n8n.cloud: Average latency: 70ms Packet loss: 0% Variation: 5.8ms (low jitter)

curl https://app.n8n.cloud/api/v1/workflows: DNS lookup: 2.3ms TCP connect: 440ms TTFB: 994ms Total: ~1 second

Conclusion: Local network is stable (70ms ping, 0% loss). Issue originates from server-side.

Impact Assessment

This issue:

  • ✅ Blocks daily automation workflows
  • ✅ Prevents production n8n deployments
  • ✅ Affects multiple users (similar reports in community.n8n.io)
  • ⚠️ May indicate backend infrastructure strain

Requested Action

Please investigate:

  1. PostgreSQL connection pool saturation
  2. WebSocket server health/reconnect logic
  3. API rate limiting or response degradation
  4. Recent deployments between April 15-16, 2026

Community References

  • Similar report: community.n8n.io/t/continuous-workflow-loading-server-connection-issues
  • Related issue: GitHub #15897 — Connection Lost Errors v1.95.2

Thank you. Please tag as High Priority given production impact.

extent analysis

TL;DR

Investigate and address potential server-side issues, such as PostgreSQL connection pool saturation, WebSocket server health, or API rate limiting, which may be causing the persistent workflow loading failures and intermittent server connection losses.

Guidance

  • Review PostgreSQL connection pool configuration to ensure it is not saturated, and consider increasing the pool size if necessary.
  • Investigate WebSocket server health and reconnect logic to determine if it is functioning correctly and make adjustments as needed.
  • Check API rate limiting settings to ensure they are not causing response degradation, and consider adjusting these settings to improve performance.
  • Examine recent deployments between April 15-16, 2026, to determine if any changes may have introduced the issue.

Example

No specific code snippet is provided, as the issue appears to be related to server-side configuration and infrastructure rather than a specific code problem.

Notes

The issue may be related to backend infrastructure strain, and addressing the potential causes listed above may help to mitigate the problem. However, further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and address potential server-side issues, as the problem appears to be related to infrastructure and configuration rather than a specific version or upgrade issue. This approach is recommended due to the high priority and production impact of the issue.

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…
#api#model download#tokenizer error#prompt formatting#API rate limit

Still need to ship something?

×6

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

Back to top recommendations

TRENDING