Implemented
0
Document several environment variables that n8n reads but the docs do not list
Source: n8n-io/n8n#40278 · opened by @shahriar-e
Bug Description We run n8n self-hosted in queue mode and set the variables below in production. The code reads them, but the environment-variable reference pages do not describe them. I checked against the n8n-io/n8n master branch and the n8n-io/n8n-docs repository at commit d833478 (2026-10-05). Not documented anywhere | Variable | Type | Default | Description (from the JSDoc in the source) | Source | |---|---|---|---|---| | N8N_EXECUTIONS_QUEUE_RECOVERY_INTERVAL | Number | 180 | How often (minutes) to check for queue recovery. Executions that a dead worker left as running get marked as crashed on this interval. | packages/@n8n/config/src/configs/executions.config.ts | | N8N_EXECUTIONS_QUEUE_RECOVERY_BATCH | Number | 100 | Size of the batch of executions to check on each queue-recovery run. | packages/@n8n/config/src/configs/executions.config.ts | | N8N_METRICS_INCLUDE_EXECUTION_DATA_METRICS | Boolean | false | Whether to include metrics for execution data reads and writes (execut…
No pledges yet. Be the first to back this.
Comments
Similar requests
n8n MCP server tool descriptions cause excessive token usage in Claude, hitting conversation limits quickly
0 votes · 0 comments
Anthropic Chat Model: expose "strict": true for client tool definitions
0 votes · 0 comments
AI Agent: return tool-schema validation failures to the model as recoverable errors instead of terminating the execution
0 votes · 0 comments
MCP tool calls fail in queue mode: `Tool node "<name>" does not have supplyData method` + `Worker tool execution timeout`
0 votes · 0 comments
Feature Suggestion: Optional token metering & paid API key support via `neuforge-pay`
0 votes · 0 comments
No comments yet.