This is the impact based on the docs and KB:
-
Deprecation Warning: Running n8n without task runners is deprecated. You will see warnings in your logs recommending you to enable task runners, as they will be turned on by default in a future version of n8n. This means that, eventually, you may be forced to use task runners as n8n evolves Task runner environment variables | n8n Docs.
-
Workflow Execution Model: Without task runners, all workflow executions (including Code node executions) happen in the main n8n process. This is the legacy behavior. Enabling task runners offloads Code node execution to separate processes, which can improve isolation and stability for complex or resource-intensive workflows.
-
Potential for Fewer Issues (Currently): Some users have reported that enabling task runners (
N8N_RUNNERS_ENABLED=true) caused issues such as workflows crashing, Code nodes not working, or performance problems. Disabling task runners resolved these issues for them, allowing workflows to run as before N8N_RUNNERS_ENABLED crash my WF, Code node doesnt work after update 1.84.1. -
No Need for Additional Configuration: If you are not using task runners, you do not need to set up the additional environment variables required for their configuration. This can simplify your setup, especially if you are running everything in a single container Task runner and environment variables: a minimum setup set.
Summary:
Disabling N8N_RUNNERS_ENABLED keeps n8n in its legacy execution mode, which may currently be more stable for some users, but it is deprecated and will not be supported in the future. You will also miss out on the isolation and scalability benefits that task runners provide. If you encounter issues with task runners, disabling them can be a temporary workaround, but you should plan to adapt your setup for future n8n releases.