[Critical] N8N SelfHosted Rollback all workflows

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
1 Like

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.

What kind of setup details do you need?

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

do you getting some response?

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

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?

I just discovered this issue as well. We lost WEEKS of updates. Completely gone. Saved, running, active scripts just completely rolled back or missing to weeks prior.

Debug info

core

  • n8nVersion: 1.116.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.18.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 9f797e82-c519-4f72-b8e0-86f66771bb3a

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 (x11; linux x86_64; rv:145.0) gecko/20100101 firefox/145.0
  • isTouchDevice: false

Generated at: 2025-11-29T02:32:48.353Z

This is nightmare fuel.

It 100% rolled back actual workflows. Every single workflow is back to how it was 2 weeks ago, I have 7 that have been updated, some significantly, entire data tables missing, it’s like someone restored a backup from two weeks ago over the top.

I am looking through logs right now and can provide them to support but this is a serious critical issue.

Ok… you guys are using n8n in production, but none has changed from SQLite to PostgreSQL as n8n suggests/recommend.

Either none of you ever tough to make a backup daily for workflows at last…

“We all learn from mistakes…almost”.

So, you can’t blame n8n for this :slight_smile:

Cheers!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.