n8n Problems & Issues
Real user-reported problems, complaints, and limitations for n8n. Based on analysis of 12 signals.
Overall score: 64/100
Issues by Category
n8n Cloud executions stuck in 'Queued / Starting soon'
Several community threads describe Cloud executions stuck in the queue for hours or days, often after an execution spike, while the UI shows no active executions. Fixes usually require a workspace restart or contacting support.
n8n webhook not working in production
Many users hit 404 'webhook is not registered' errors because n8n has separate test and production webhook URLs and the production one only works while the workflow is active/published. Self-hosted instances behind a proxy also show localhost URLs until WEBHOOK_URL is set.
n8n 2.0 update broke existing workflows
Version 2.0 removed the Start node, Pyodide Python Code node, MySQL storage and in-memory binary mode, blocks env var access in Code nodes, disables Execute Command by default and replaces Activate with Publish. Self-hosters who updated without reading the breaking-changes list saw workflows fail.
n8n is too hard for non-technical users
The most common complaint on G2 is a steep learning curve, especially for people unfamiliar with APIs, JSON and branching logic. Advanced workflows often need JavaScript in the Code node, which undercuts the no-code pitch.
Self-hosting n8n is more work than expected
Free self-hosting means you handle reverse proxies, WebSockets, backups, Postgres, upgrades, monitoring and your own OAuth apps for Google or Slack. Losing the encryption key makes stored credentials unusable.
n8n error messages don't explain what went wrong
Users report blank errors and generic messages such as 'Cannot read properties of undefined' or 'Connection lost' that don't point to the cause. G2 reviewers ask for better debugging tools.
Large n8n workflows become hard to manage
Reviewers say the canvas gets unwieldy as workflows grow, and G2 users mention slowness compared with other apps. Splitting logic into sub-workflows is the usual workaround.
Critical n8n security vulnerabilities on self-hosted instances
Six critical CVEs were disclosed between January and March 2026, including CVE-2026-21858 (unauthenticated remote code execution on internet-exposed instances), and an October 2026 bulletin covered eight more, five rated High. Self-hosters must patch quickly and keep instances behind a reverse proxy.
n8n runs out of memory on large data and files
Big JSON payloads, binary files, Code nodes and manual test runs can exhaust memory, producing 'Execution stopped at this node (n8n may have run out of memory)' or 'JavaScript heap out of memory'. n8n's own docs recommend batching, sub-workflows and more RAM.
n8n support is slow and hard to reach
Trustpilot 1-star reviews (37% of 49) mostly cite email-only support, slow replies and account lockouts with no recovery path. Community forum threads describe cloud workspaces offline for days with no ETA. Self-hosters on the free edition get forum support only.
n8n Google OAuth redirect_uri_mismatch errors
Connecting Google Drive, Gmail or Sheets often fails with redirect_uri_mismatch, both on self-hosted instances using localhost URLs and on n8n Cloud, where users reported a mismatch between the displayed and sent redirect URL that was fixed in a later release.
Why is n8n Business so expensive?
Cloud Starter and Pro are cheap, but SSO, Git version control, multiple environments and queue mode sit in the self-hosted Business plan at about €667/month billed annually, with overage buckets of €4,000 per 300k executions. Starter caps executions at 5 minutes and keeps 7 days of logs.
Regret Patterns
Common reasons users regret choosing n8n.
Picked n8n to avoid code, ended up writing JavaScript
Non-technical users expect no-code, then find that data transformations and edge cases need Code node scripts and expressions.
Self-hosted to save money, then spent the savings on maintenance
Proxy, WebSocket, OAuth, backup and upgrade issues consume hours that outweigh the subscription savings.
Exposed instance needed emergency patching
Self-hosters running internet-facing instances had to rush updates after critical CVEs were disclosed in 2026.
Upgraded and workflows broke
Pulling the latest image without reading breaking changes (notably 2.0) disabled nodes and broke Code node behavior.
Cloud outage with no support response
Cloud users report workspaces offline or executions stuck for days while waiting on email support, with clients affected.
Needed SSO or Git and hit the Business price wall
Teams that grow into needing SSO, environments or version control find those features only in the much pricier Business plan.
When n8n Breaks Down
Specific scenarios where n8n fails or underperforms.
Processing thousands of rows or large files
Memory spikes cause 'n8n may have run out of memory' errors unless data is batched and split into sub-workflows.
Self-hosting behind nginx, Traefik or Plesk
Missing WebSocket upgrade headers or wrong N8N_PROXY_HOPS cause 'Connection lost' and 'Invalid origin' errors in the editor.
Execution spikes on n8n Cloud
Bursts of executions can leave runs stuck in 'Queued / Starting soon' until the workspace is restarted.
Major version upgrades
Breaking changes like those in 2.0 disable nodes and change Code node behavior.
Long-running workflows on Starter
Starter caps executions at 5 minutes, so long AI or scraping jobs fail unless you upgrade or split them.
Connecting Google services on a self-hosted instance
You need your own Google Cloud OAuth app, and a wrong public URL produces redirect_uri_mismatch errors.