Possible Bug: Data loss with Notes

There was no crash, but I'm pretty sure I experience data loss today.

I agree that it's improbable and I probably am mistaken.

When I'm working on a sermon, I always create a note in a Notebook called "Scrap" for the purpose of cut/pasting sentences and paragraphs that I decided were not worth keeping in the final sermon, but I wanted to store somewhere in case I changed my mind.

For my evening sermon this week, I created such a note, and if memory serves me correctly, copy/pasted lots of things into it, and now when I open it it looks like it did just after I created it (with just a title, "Revelation 1:9-20").

I'm attaching my logs (I don't know why the Logos.log file is 3 days old and not updated as of today).

0407.LogosCrashDeletedNoteContent.zip

Find more posts tagged with

Comments

Dave Hooton

There was no crash, but I'm pretty sure I experience data loss today.

I agree that it's improbable and I probably am mistaken.

..

I'm attaching my logs (I don't know why the Logos.log file is 3 days old and not updated as of today).

A bit older, and therefore not useful to your issue.

A little improbable, but have you checked notes created/modified on the same day? Have you checked Trash?

Have you attempted to recreate that Note (I realise you can't recreate the lost data), ensuring that logging is enabled e.g. start Logos with CTRL held down.

Robert Kelbe

https://community.logos.com/discussion/comment/1271173#Comment_1271173

A bit older, and therefore not useful to your issue.

A little improbable, but have you checked notes created/modified on the same day? Have you checked Trash?

Have you attempted to recreate that Note (I realise you can't recreate the lost data), ensuring that logging is enabled e.g. start Logos with CTRL held down.

I agree. However, I enabled logging when I joined Beta and I never turned it off, so I thought the lack of up-to-date logs might be somehow relevant. I have also experienced slowness with Sermon Editor which someone reading the logs said was due to some kind of sync error.

I sorted by last modified and also searched my notes for a keyword I thought would be there.

I’ll just keep an eye on it if it happens again. I do the same thing every week.

Dave Hooton

https://community.logos.com/discussion/comment/1271185#Comment_1271185

However, I enabled logging when I joined Beta and I never turned it off, so I thought the lack of up-to-date logs might be somehow relevant

I did wonder about that, as FL state that logging is permanently enabled for the Beta releases. It is possible that they turned it off for the RC releases (RC1 was Sept 5th and your Logos.log finished on Sept 6th). The LogosError.log is always enabled, but lacks the detailed info we need from the Logos.log.

I have also experienced slowness with Sermon Editor which someone reading the logs said was due to some kind of sync error.

There were a number of sync errors in Logos.log from 1st September, but they affected a number of features in addition to Sermon Writer, and had been resolved by Sept 3 (Logos.log finished early on Sept 6). The Error log picked up single occurrences on Sept 6, 7 and 8 and 4 occurrences on Sept 9.

You should re-enable logging.

Andrew Batishko

https://community.logos.com/discussion/comment/1271237#Comment_1271237

However, I enabled logging when I joined Beta and I never turned it off, so I thought the lack of up-to-date logs might be somehow relevant

I did wonder about that, as FL state that logging is permanently enabled for the Beta releases.

Logging is permanently enable for beta builds, but an RC is not considered a beta. Therefore, the recorded log is probably from the last time Robert ran Beta 4.

Dave Hooton

https://community.logos.com/discussion/comment/1271240#Comment_1271240

Logging is permanently enable for beta builds, but an RC is not considered a beta.

Thanks for the confirmation. It occurred to me after I posted (as per my late Edit).

Robert Kelbe

https://community.logos.com/discussion/comment/1271242#Comment_1271242

I re-ran the script to turn logging on, but I'm still not sure what caused it to be turned off...