So I upgraded to 1.87.0 a few days ago and my workflows started failing due to SQLite errors (example below). I was going to submit a bug report but while digging noticed my database file had risen to about 10 gigs in size… turns out I’d never enabled pruning.
Before I waste anyone’s time with an actual bug report, is this the likely cause? I’ve since enabled pruning and vacuuming on startup, which dropped the size to a much more manageable 1 gig. No errors yet, but we’ll see.
{
"execution": {
"id": "64050",
"url": "url/workflow/cbxfqmEB2YSLsyWn/executions/64050",
"error": {
"query": "SAVEPOINT typeorm_-2",
"driverError": {
"errno": 1,
"code": "SQLITE_ERROR",
"__augmented": true
},
"errno": 1,
"code": "SQLITE_ERROR",
"__augmented": true,
"message": "SQLITE_ERROR: near \"-\": syntax error",
"stack": "QueryFailedError: SQLITE_ERROR: near \"-\": syntax error\n at handler (/usr/local/lib/node_modules/n8n/node_modules/@n8n/typeorm/driver/sqlite/SqliteQueryRunner.js:88:37)\n at replacement (/usr/local/lib/node_modules/n8n/node_modules/sqlite3/lib/trace.js:25:27)\n at Statement.errBack (/usr/local/lib/node_modules/n8n/node_modules/sqlite3/lib/sqlite3.js:15:21)"
},
"lastNodeExecuted": "Check Network",
"mode": "trigger"
},
"workflow": {
"id": "cbxfqmEB2YSLsyWn",
"name": "workflow name"
}
}