n8n
n8n Workflow Force-Stopped After Hours? Fix Out-of-Memory Crashes with Batch Processing
n8n workflows dying after hours with no node error are usually memory kills. Diagnose the crash, then fix it with batching, execution pruning, and heap caps.
n8n workflows dying after hours with no node error are usually memory kills. Diagnose the crash, then fix it with batching, execution pruning, and heap caps.
Run n8n in queue mode: a main instance plus Redis-backed worker processes for parallel executions. Docker Compose setup guide, verified on n8n 2.41.4.