Db corrupted due to recent bug

My db got corrupted, so whenever I try to import it by importing db as a new graph I get the following error:
Invalid data writing to db!

**SQLiteDB import error: #error {:message “DB write failed with invalid data”, :data {:tx-meta …….}}

It does show my graphs and pages but I cannot export it and every item I open logseq I get Invalid data writing to db!

How do I fix my db so I can continue working on it again

1 Like

Probably due to this After updating to the latest DB version (released on May 3), my data cannot be read. · Issue #12558 · logseq/logseq · GitHub

Please help, even my hourly backups are affected, how do I identify and fix the affected blocks

What version of the app are you using? Are you on web or desktop?
Make sure to install the latest version and retry.

If the issue persists, open the console: Toggle Developer Tools: F12 or Ctrl+Shift+I (Win) / Cmd+Option+I (Mac). and capture the errors you see and share.

Side note, the testing and discussion about logseq DB during this phase is happening in Discord where there is a lot more activity at this moment.

1 Like

On Desktop version, from latest pipeline 2.0.1-alpha+nightly.20260505

Every time I import notes from my db.sqlite I get
https://privatebin.app/?c7a0111a0ac14dec#HHYPZ7kDSb5jqShgDsZLU1aLZCCE4Qgs2jDA8PVW89U2

and when I open the graph again I cannot even use the logseq , first it keeps on loading no pages are shown and If I try to do something it crashes with
https://privatebin.app/?4e629cd43e6d7bb3#66V62WcDZiT3jnaMcH9o6QFF3QJV7gzH6ZuseSTQYP8M

I have multiple backups from 1may, 30Apr, 29 apr and even 19 apr , they all are having the same issue when importing