n8n Webhook and Queue Troubleshooting Checklist

Webhook URL and mode

Webhook URL and mode Confirm whether the caller is using the test URL or production URL. If using the production URL, confirm the workflow is active. Check the Webhook node path and HTTP method. For self-hosted n8n, confirm WEBHOOK_URL and the public domain match the real external URL.

Reverse proxy and browser access

Reverse proxy and browser access Confirm the reverse proxy forwards webhook paths to n8n. Check whether the proxy rewrites or strips paths. For browser calls, confirm the Webhook node allowed origins and proxy CORS headers. Test externally, not only from the server.

Queue mode and workers

Queue mode and workers Confirm main and worker processes use EXECUTIONS_MODE=queue. Check Redis host, port, password, and database from both main and worker containers. Confirm workers share the same n8n database and N8N_ENCRYPTION_KEY. Run a small workflow and verify a worker completes the execution.

Data and payload failures

Data and payload failures For invalid JSON, inspect the exact runtime payload, not just the template. For expressions, confirm referenced nodes executed on the current branch. For rate limits, add delay, batching, or Loop Over Items before retrying at scale. For OAuth callbacks, copy the exact callback URL from n8n into the provider app.

When To Use It

Use this when a workflow worked in the editor but fails from an external app, when jobs stay queued, when workers look healthy but do not process executions, or when browser/API calls fail before the workflow logic is reached.

This is an independent third-party checklist. It links back to source-backed Workflow Fixes pages and official n8n documentation for verification.

n8n webhook and queue troubleshooting checklist

Checked Context

Webhook URL and mode

Reverse proxy and browser access

Queue mode and workers

Data and payload failures

When To Use It

Related Fix Pages