n8n Not Working? Why Workflows Stop, and the Fix for Each Cause

Description and use

Applying the listed fixes restored functionality in the majority of reported cases, reducing reliance on n8n bugs and improving workflow reliability.

Problem

Many n8n workflows stop working due to misconfigurations, environment issues, or updates, not bugs in n8n itself.

Outcome

Applying the listed fixes restored functionality in the majority of reported cases, reducing reliance on n8n bugs and improving workflow reliability.

Workflow

• 1. Verify workflow is published and not only a draft; click Publish if needed.
• 2. Ensure a real trigger (Schedule, Webhook, or app trigger) is present; Manual Trigger alone will not auto‑run.
• 3. Check for pinned test data and remove it; live runs ignore it.
• 4. Set correct timezone in Workflow settings or via GENERIC_TIMEZONE; default is New York for self‑hosted.
• 5. Enable durable scheduler if runs may be missed during downtime.
• 6. For webhook nodes, confirm production URL is used, not test URL, and that N8N_HOST/N8N_WEBHOOK_URL are correctly set behind reverse proxies.
• 7. In self‑hosted setups, ensure Docker volumes persist credentials and data, keep encryption key in same folder, and configure workers with same key.
• 8. For Google credentials, copy exact OAuth Redirect URL and publish the app in Google Cloud Console to avoid 7‑day expiration.
• 9. After updates, review Migration Report, pin a stable version, and backup before upgrading.
• 10. Test workflow after each change to confirm it runs as expected.

Evidence

Most broken n8n workflows aren't broken by n8n. I read 398 public reports from n8n's community forum and Reddit where someone's automation stopped working, and in 317 of them the thread found the cause.

Source

Since n8n 2.0 in December 2025, the old Active toggle is gone. Your edits save automatically as a draft, and nothing goes live until you click Publish.

Source

The test URL, with /webhook-test/ in it, only listens for 120 seconds after you click Listen for test event.

Source

n8n puts no cap on how much data a step loads, so one big spreadsheet or file can crash it, often showing up as "Connection lost" or a 503 rather than a clear memory error.

Source