Task runner timeout on n8n Cloud - Code nodes failing for a week

Questions
15

+1, I’m seeing the same on self-hosted as well, but only in one specific workflow. Most of my other workflows run fine.

I already tried increasing N8N_RUNNERS_TASK_TIMEOUT, but that didn’t change anything.

What did help was reducing the amount of input data passed into the Code node by batching (using the Loop/Batching approach). In my case:

  • 1000 rows at once fails basically every time

  • ~500 rows sometimes fails

  • ~100 rows has been stable so far

I also checked the logs, but there’s nothing obvious or suspicious around the failures.

These are the task-runner-related environment variables I explicitly set:

N8N_RUNNERS_ENABLED=true
N8N_RUNNERS_MODE=external
N8N_RUNNERS_AUTH_TOKEN=${N8N_RUNNERS_AUTH_TOKEN}
N8N_RUNNERS_BROKER_LISTEN_ADDRESS=0.0.0.0
N8N_RUNNERS_TASK_REQUEST_TIMEOUT=120
N8N_RUNNERS_TASK_TIMEOUT=300
N8N_RUNNERS_MAX_CONCURRENCY=20
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true