[Critical] N8N SelfHosted Rollback all workflows

Questions
, ,
1

My n8n rollback all workflows to an outdated version.

Recently I’ve been facing a big problem; this is the second time on Mondays that I’ve experienced a rollback to October 26th. I don’t know why this is happening, if it was something misconfigured or something I might have done, but we’ve been using n8n for months and only recently started experiencing this.

Information on your n8n setup

  • n8n version: 1.113.3
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default i guess
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: ubuntu selfhosted docker in digital ocean
2

Sounds like something isn’t set up right with the persistent volume.
Could you share your setup details?

Also I recommend using postgres when using n8n for production flows.

3

What kind of setup details do you need?

4

I have a very similar issue to this: Setup is via docker (Compose), and the debug info is below. I also made a post about it here: N8N keeps undoing changes, Data Tables change, Archived Workflows keep returning, saved and tested changes keep getting undone : r/n8n:

instance information

Debug info

core

  • n8nVersion: 1.117.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.18.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 4a647dca-2b4a-43d7-bb8d-027796dc2ef4

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36 edg/142.0.0.0
  • isTouchDevice: false

Generated at: 2025-11-04T16:26:29.182Z

1 Like
5

do you getting some response?

6

You both are using SQLLite, typically rollbacks of data, can be attributed to SQL database itself if some of the data isn’t committed. If its a data problem, look at whats commiting it to the database, if its rolling back actual workflows and other things… well, that maybe a different story

7

The strange thing from my point of view is that it is seemingly random. I can be working on a workflow save it, leave it running for a few days and then it reverts sometimes days into the past.

Although it seems to have been stable for a few days now…

Is there a way to change from SQLite to a different DB when using Docker?