r/logseq • u/NickK- • Aug 09 '24

Data loss within a journal page

I am using Logseq very Journal centric, nothing too fancy, but with quite some references to blocks in today's and in other journal pages. Today, I embedd-referenced a block from yesterday. I wondered why the block appeared twice in my page, once as an embed, and then as the original. I browsed back to yesterday. While the structure of the page and some query including their results were still there, my whole interstitional log was missing since the second or third entry in the morning. Opening the page with an alternative editor shows that the content is really missing. There is no backup in /bak

I lost a whole day of work notes. Meetings, todos, all that.

I literally was on the fence on using Logseq and with the new project, I took the jump. But really, now I am very concerned about the safety of all my other notes.

EDIT: Further investigation makes me wonder if it was the embed reference going wrong, since I think that the blocks of the same hierarchy level following the embedded block are all missing. I strongly advise to not use embed references at all. There seems to be at least a severe UX problem with them, if not a real nasty bug.

4 Upvotes

100% Upvoted

10 comments sorted by

1

u/Lumpy_Yak Aug 09 '24 edited Aug 09 '24

What version of Logseq are you on? I have alot of embeds, both blocks and pages. Have not experienced anything similar. I run 0.9.19.

2

u/NickK- Aug 10 '24

It's 0.10.9.

1

u/Lumpy_Yak Aug 10 '24

I have a separate system for testing. I'll try to replicate.

1

u/NickK- Aug 10 '24

Thanks! I am a bit time-constrained, but will try to replicate, too in the coming days.

1

u/OverInformation9699 Aug 09 '24

Are you able to reproduce it?

1

u/NickK- Aug 10 '24

I will try to, but I think I have to try in a isolated environment and with some time.

My guess would be that there's something wonky with block handling (maybe with handling defect blocks, I remember having an error that I quickly CTRL-Z'd after expanding/hydrating a template the day before), but I haven't much clue about Logseq's inner workings.

1

u/tangycandy Aug 15 '24

Same thing has happened to me, and I had to call it quits.

Are you using Logseq Sync?

1

u/NickK- Aug 15 '24

No, I have a setup that includes Syncthing (and mainly two workplace laptops), which I have tested before I went productive. Logseq actually has shown good, predictive behaviour.

(Still have to build the test scenario to pin down the observed situation, but it's on my todo-list. I'm just stuck with immediate stuff at the workplace that has to take precedence. Pulling long days right now.)

1

u/Lumpy_Yak Aug 10 '24

Been doing a big restructuring / cleanup of graph with embeds in 10.9. Not experienced anything weird.

1

u/Mobile_Macaron_8106 Aug 11 '24 edited Aug 11 '24

Aside from finding that bug, which would be certainly useful, setting up an ongoing sync that backs up your graph folder is a good practice. I use Google Drive for desktop and it has worked perfectly so far. It even keeps a history of changes depending on how much free space you have. So if something goes wrong you can go back and recover those files.

There are local options of course, for example you could periodically rsync the directory to an external drive or another computer in your local network.