Have you searched for an existing feature request?

• Yes, I tried searching

Brief Summary

Love your program, thank you so much for your work on it. I wanted to write about an issue I've faced with data loss in a couple of scenarios.

Per screenshot, when a file has a old or new entry that's in the process of being edited and the database is saved, the save is halted and a user prompt comes up to ask if the changes should be discarded and database locked, or save cancelled so editing can continue. This effectively stops auto-save from working as desired in several scenarios.
Please either allow the save to complete, and mark the entry (AUTOSAVED) so that users are aware of the save. Or add it as an option, eg 'auto-save new and edited entries'. Either way will allow the end-user the ability to know what's happened and no data will be lost.

As an aside - I think the prompt is confusing because it doesn't follow standard UX design cues. When a potentially destructive option is offered to the user, the least destructive option should be leftmost as the 'default' choice. In this case, the rightmost option is the least potentially destructive.
Also the choice in a user prompt should aim to be binary whenever possible: eg the prompt for an automatic save & lock the user has requested/configured being blocked should be something like: "Ignore blocking issue (save & lock)", or "Cancel (HALT save & lock)". Not "Ignore blocking issue & Cancel new/edited entry & Save & Lock", or "Cancel (HALT save & lock)".

Example

Any NEW entry in editing would be automatically saved when 'auto-save on lock' is enabled, I feel like that is a no-brainer as it does not ever risk data loss, simply risks new entries having incomplete names or data which the user could continue editing later, or delete if the entry is not desired.

Any PRE-EXISTING entries in editing would to be automatically saved, as that is the option that risks losing least data - even if an entry has undesired changes, the prior version of the entry will still be available in the version history of that entry, so the user could revert any unintended changes. Ideally marking entries saved in this manner in some way (for example simply adding "(AUTOSAVED)" to the entry name) to highlight to the user that a change was made by the program to an entry they were editing when it autosaved.

Context

I've lost data on an entry twice now, first because I was confused by the prompt and clicked 'Discard' as it is the default (leftmost) option, and second loss was because I was afk while a new entry was awaiting additional notes, and there was an extended power outage overnight. One of those required significant hassle to get my password reset with the provider.
I've been extra careful anytime I see that prompt come up now, makes my heart skip when I see it as I know I need to read it a few times to ensure I'm clicking the option I really want to avoid losing data again.