Deploy n8n Workflows via CLI, Not SQLite
Editing workflow JSON directly in SQLite leaves a stale activeVersionId and produces the 'all-green, nothing happens' ghost. The CLI import + publish path is the correct deploy.
Editing workflow JSON directly in SQLite leaves a stale activeVersionId and produces the 'all-green, nothing happens' ghost. The CLI import + publish path is the correct deploy.
When sqlite3 .recover is unavailable, the .dump-and-COMMIT trick rescues a corrupt database. A real fix for n8n's execution_data btree corruption.