Logseq messes up data when started while external sync is running

I think this can’t really be fixed in Logseq but it should probably be mentioned in the docs.

What happened

I ran now several times into a situation in which I opened Logseq in the morning on my desktop PC and the following had happened:

  • The previous day’s journal is empty
  • The current day’s journal contained the journal template followed by the full contents of the previous day’s journal file
    In any of the cases, I had made changes to the previous day’s journal in the evening on my laptop.
    I did some testing and figured out that this only happens when I start Logseq on my desktop PC while the external sync (in this case Nextcloud) is still running.

My setup

  • 1x Desktop PC running Ubuntu 22.04 and Nextcloud Desktop Client
    – Nextcloud Desktop client is set to autostart
    – Logseq is usually the first app I open in the morning right after the PC is up
  • 1x Laptop running Ubuntu 22.04 and Nextcloud Desktop Client
    – Nextcloud Desktop client is set to autostart
  • 1x Android 8.1 phone running Folder Sync Pro
  • 1x Android 10 tablet running Folder Sync Pro

Sync config

  • $HOME/logseg (data directory): full
  • $HOME/.logseq: ./graphs and ./git excluded

Because I have versioning activated on the Nextcloud server, I could easily revert the changes but it’s something that needs to be remembered…: Do not start Logseq before the initial sync after boot has finished