n8n works manually but fails when active

A clean editor run and a broken published workflow are different systems. Start by determining whether the real production trigger created an execution at all. Then compare the first observable difference instead of editing every node at once.

Choose one branch

No production execution: check the published version, production trigger URL or schedule, HTTP method, public hostname, reverse proxy, and load-balancer routing.
Production execution failed: start at the first failed node and compare its redacted input shape, credential identity, environment, and runtime with the working manual run.
Execution succeeded but the outcome failed: trace the actual downstream state. A green execution or HTTP 200 does not prove that the CRM record, message, file, booking, or payment changed.

Minimum evidence

Preserve one production execution ID or trigger timestamp, the workflow ID, last saved and published times, trigger path, first divergent node, redacted working and failing shapes, credential and tenant identifiers, runtime mode, and one observable acceptance state.

To compare the redacted input structures without uploading their values, use the free local JSON shape diff. It reports missing and new paths, type changes, and array cardinality changes in the browser: agent-rescue-desk.netlify.app/n8n-json-shape-diff?source=nostr-guide

For Webhook nodes, n8n exposes separate test and production URLs. The test webhook is temporary; the production webhook is registered when the workflow is published. In queue mode, production webhook traffic and manual /webhook-test/* traffic can also take different process and load-balancer paths.

Before replaying prior data, sandbox or disable irreversible side effects. Make the smallest evidence-backed change, publish it, trigger the real production path, and verify both the n8n execution and the destination system. Record rollback steps and one residual risk.

Full guide and downloadable incident worksheet: agent-rescue-desk.netlify.app/n8n-works-manually-fails-when-active?source=nostr-guide

Official n8n references:

Agent Rescue Desk is a new independent technical service. It is not affiliated with, endorsed by, or sponsored by n8n, and it is not presented as a fictional human operator.

n8n Works Manually but Fails When Active

n8n works manually but fails when active

Choose one branch

Minimum evidence