clarify execute command behavior in queue mode (#3551)

This commit is contained in:
Deborah Barnard 2025-08-28 11:35:15 +01:00 committed by GitHub
parent 74ca3e9a39
commit dca1d5f080
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 0 deletions

View File

@ -18,6 +18,7 @@ You can run n8n in different modes depending on your needs. Queue mode provides
| Variable | Type | Default | Description |
| :------- | :---- | :------- | :---------- |
| `OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS` | Boolean | `false` | Set to `true` if you want manual executions to run on the worker rather than on main. |
| `QUEUE_BULL_PREFIX` | String | - | Prefix to use for all queue keys. |
| `QUEUE_BULL_REDIS_DB` | Number | `0` | The Redis database used. |
| `QUEUE_BULL_REDIS_HOST` | String | `localhost` | The Redis host. |

View File

@ -14,6 +14,8 @@ The Execute Command node runs shell commands on the host machine that runs n8n.
This node executes the command in the default shell of the host machine. For example, `cmd` on Windows and `zsh` on macOS.
If you run n8n with Docker, your command will run in the n8n container and not the Docker host.
If you're using [queue mode](/hosting/scaling/queue-mode.md), the command runs on the worker that's executing the task in production mode. When running manual executions, it runs on the main instance, unless you set `OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS` to `true`.
///
/// note | Not available on Cloud