n8n errors / Config
SQLITE_BUSY: database is locked
Cause
SQLite allows only one writer at a time; concurrent workflow executions writing simultaneously cause SQLITE_BUSY.
Fix
Migrate to PostgreSQL for any instance running concurrent workflows - SQLite is for single-user dev only. If migration must wait, set EXECUTIONS_PROCESS=main to serialise executions. On NAS/Azure file shares, move the SQLite file to local container storage (remote mounts have poor SQLite locking).
Part of the Automation Error Index — n8n errors: browse all.
Hitting an automation error we have not covered?
AutomateLab builds and debugs n8n, Make, and agent workflows as fixed-scope projects. If something is broken in production, tell us what you are seeing.
Describe the problem