I tried to search for someone having the same issue on the forum but didn’t find the thread. Sometimes when I close and open Devonthink again, it doesn’t keep my databases loaded. I then need to open these again… It’s not a big issue but it’s just sometimes annoying…
Does someone had the same issue? (I’m using the last version of Catalina)
This should actually only happen after a crash or force quit. One workaround to easily open multiple databases is to use workspaces (see Go menu).
Correct! however I have noticed occasionally does happens when closing normal.
I dont really mind it, it happens sometimes
Maybe it’s not related but since I bought the Pro licence, it seems not happening as often 
And just to confirm, it was happening after closing normal Devonthink.
Licenses don’t affect this behaviour actually.
I’m getting the same issue every few days - but it’s not consistent and I can’t associate the behaviour with any DT or non-DT events on the Mac. As you say, not a big issue but mildly annoying.
Does this e.g. happen after updating/restarting the computer or logging out while DEVONthink was running?
Nope, it happens during the same session.
Same behavior happens for me. I’ll often have previously open databases randomly closed when I reopen DT.
Are some of them located on unmounted volumes?
For me no. All the databases are inside a folder at the root of my HD.
Mine are in my documents folder. Always mounted
Is the Documents folder synchronized via iCloud?
No , I don’t use iCloud
I have started having to reopen databases as well since DT3. Not each time, but sometimes.
I also find the re-opening sometimes to be very slow, whereas DT2 never took so long. Sometimes I have to restart.
Sometimes I have to restart.
Please clarify what this means in this context.
Sorry. I mean that I get the spinning wheel for half an hour or so, sometimes, after only one or two of the DBs out of 13 opening. So I elect to force quit DT. It tends to be after I have been away for a week or so, not if I open it every day.
Hold the Option key and choose Help > Report bug to start a support ticket.
Also, when the application is stalled, do a Spotlight search for Activity Monitor. Select our application in the list of processes - it should show “(Not Responding)” and the name in red - and press Command-Option-S to run a sample on it. When the sample window opens, press the Save button and save it to your Desktop. Please attach this text file to your Support Ticket so we can inspect it.