Skip to main content
n8n supports different execution modes for running workflows, each optimized for specific use cases and scaling requirements.

​
Execution Modes Overview

Regular mode executes workflows directly in the main process. This is the default mode for single-server deployments.
n8n start
Best for:
  • Development environments
  • Small to medium deployments
  • Simple setups without scaling needs
Characteristics:
  • All workflows run in the main process
  • Simple architecture
  • No external dependencies (like Redis)
  • Limited horizontal scaling

​
Configuration

Set the execution mode via environment variable: 
export EXECUTIONS_MODE=regular
n8n start

​
Worker Process

Workers handle workflow executions in queue mode.

​
Starting Workers

n8n worker

​
Worker Flags

​
--concurrency
number
default:"10"
Maximum number of jobs a worker can run simultaneously.
Examples: 
n8n worker --concurrency=3
Performance Tip: Workers with concurrency below 5 may experience instability. Set to at least 5 for production use.

​
Worker Environment Variables

VariableDescriptionDefault
N8N_CONCURRENCY_PRODUCTION_LIMITOverride concurrency setting-1 (disabled)
N8N_GRACEFUL_SHUTDOWN_TIMEOUTSeconds to wait before force shutdown30
Example: 
export N8N_CONCURRENCY_PRODUCTION_LIMIT=15
n8n worker

​
Webhook Process

Dedicated webhook handling for improved performance and reliability.

​
Starting Webhook Process

n8n webhook
Webhook processes require queue mode. They cannot run in regular execution mode.

​
Benefits of Separate Webhook Process

  • Isolation: Webhook handling separated from main process
  • Scalability: Run multiple webhook processes
  • Reliability: Webhook failures don’t affect main instance
  • Performance: Dedicated resources for webhook traffic

​
Architecture Example

# Terminal 1: Main instance
n8n start

# Terminal 2: Webhook process
n8n webhook

# Terminal 3: Worker process
n8n worker --concurrency=10

# Terminal 4: Additional worker
n8n worker --concurrency=10

​
Multi-Main Setup

For high availability, run multiple main instances (Enterprise feature).
Multi-main setup requires a valid n8n Enterprise license with the “Multiple Main Instances” feature enabled.
Configuration: 
export EXECUTIONS_MODE=queue
export N8N_MULTI_MAIN_SETUP_ENABLED=true

# Start multiple main instances
n8n start  # Instance 1
n8n start  # Instance 2
n8n start  # Instance 3
Features:
  • Leader election for coordinated operations
  • Shared workflow execution queue
  • High availability
  • Zero-downtime deployments

​
CLI Execution

Execute workflows directly from the command line.

​
Execute Single Workflow

n8n execute --id=WORKFLOW_ID
​
--id
string
required
The workflow ID to execute.
​
--rawOutput
boolean
default:"false"
Output only JSON data without additional text.
Examples: 
n8n execute --id=abc123

​
Execution Behavior

  • Always executes in CLI mode (not as webhook or trigger)
  • Starts from the workflow’s designated start node
  • Does not support queue mode (automatically falls back to regular)
  • Useful for testing and debugging

​
Batch Execution

Execute multiple workflows for testing purposes. 
n8n execute-batch --ids=1,2,3 --concurrency=5

​
Common Batch Scenarios

Run all test workflows with output:
n8n execute-batch \
  --output=/results/test-run.json \
  --concurrency=10 \
  --retries=2

​
Skip List Format

Create a JSON file to skip specific workflows: 
[
  {
    "workflowId": "123",
    "status": "broken",
    "skipReason": "Known issue with external API",
    "ticketReference": "JIRA-456"
  },
  {
    "workflowId": "456",
    "status": "deprecated",
    "skipReason": "Workflow being replaced",
    "ticketReference": "JIRA-789"
  }
]

​
Execution Context

Understanding how workflows execute in different contexts:
ContextTriggerUse Case
CLIn8n executeTesting, debugging
WebhookHTTP requestExternal integrations
TriggerTime/eventAutomated workflows
ManualUI buttonUser-initiated

​
Performance Tuning

​
Worker Optimization

# More workers, lower concurrency
n8n worker --concurrency=5  # Worker 1
n8n worker --concurrency=5  # Worker 2
n8n worker --concurrency=5  # Worker 3

​
Concurrency Guidelines

Server SpecsRecommended Concurrency
2 CPU, 4GB RAM5-8
4 CPU, 8GB RAM10-15
8 CPU, 16GB RAM20-30
16+ CPU, 32GB+ RAM40+
These are starting points. Monitor CPU, memory, and queue length to optimize for your specific workloads.

​
Monitoring Execution

​
Worker Status

Workers log their status on startup: 
n8n worker is now ready
 * Version: 1.70.0
 * Concurrency: 10

​
Health Checks

Enable health check endpoints for monitoring: 
export QUEUE_HEALTH_CHECK_ACTIVE=true
n8n worker
Health endpoint: http://localhost:5678/healthz

​
Troubleshooting

Problem: Workflows remain in “running” state but don’t execute.Solutions:
  • Check if workers are running: ps aux | grep "n8n worker"
  • Verify Redis connection
  • Increase worker concurrency
  • Check worker logs for errors
Problem: Worker process terminates unexpectedly.Solutions:
  • Reduce concurrency (may be overloaded)
  • Check memory limits
  • Review workflow complexity
  • Enable debug logging
Problem: Executions run in main process despite queue mode.Solutions:
  • Verify EXECUTIONS_MODE=queue is set
  • Check Redis connection string
  • Ensure Redis is running and accessible
  • Check for configuration conflicts

​
Next Steps

CLI Commands

View all available CLI commands

Configuration

Configure execution settings

Scaling

Learn about scaling n8n

Queue Mode

Detailed queue mode documentation