N8N_RUNNERS_ENABLED in webhook processor

[yukyo]

Describe the problem/error/question

I’m running an n8n setup with the following architecture:

• 1 main instance (editor only)
• 1 webhook processor
• 4 workers

Current Configuration:

Main instance (.env):

N8N_PROXY_HOPS=1
N8N_RUNNERS_ENABLED=true
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

Workers (.env):

N8N_RUNNERS_ENABLED=true

Issue: When deploying the webhook processor, I’m seeing this deprecation warning:

- N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set `N8N_RUNNERS_ENABLED=true` to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/

Questions:

1. Does the webhook processor require N8N_RUNNERS_ENABLED=true like the workers?
2. What’s the proper configuration for the webhook processor? Should it include additional settings beyond just enabling runners?
3. Address configuration: Does the webhook processor need to run on the same address as the workers, or can I simply add N8N_RUNNERS_ENABLED=true and let it use the default 127.0.0.1 address?

Is it normal that when the webhook processor runs without N8N_RUNNERS_ENABLED=true, adding a second webhook processor causes the MCP nodes to stop working? Is this related to the fact is not running with N8N_RUNNERS_ENABLED=true?

Any guidance on the recommended webhook processor configuration would be appreciated.
Thanks!

Information on your n8n setup

• n8n version: 1.115.3
• Database (default: SQLite): Postgresql
• n8n EXECUTIONS_PROCESS setting (default: own, main): queue
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker

[yukyo]

I tried enabling N8N_RUNNERS_ENABLED=true in the webhook processor and as expected, MCP requests don’t work anymore…