I used to have a Tidal and Qubuz account, streamed via my 2i , and never had that issue.
Just Qb now and no issues , but I never turn mine off.
As I have a 2Tb external hard drive connected to the USB, it rebuilds the index each time i turn it on, takes over an hour , so it's always on here.
Might be the solution?
My Vault 2 is always left on unless it gets so muddled that a power cycle is required.
The only things in my set-up that are turned off after use are my Croft preamp and power amp because they contain valves. Everything else is left on and ready to go, including the Vault 2.
Since a lot of internet stuff is based around messaging, and since a lot of internet issues arise from messages that are either sent but never received, or are received but never acknowledged, it might be that, although your Nodes think that you're logged into Tidal and tell you so, in fact they aren't because you've powered off your Nodes and severed the connection to Tidal without logging off.
In such an instance, the Node would probably see a locally stored (stored on the Node) "logged in" status (as it never actually witnessed you logging off) whereas the Tidal server itself will have seen no activity or responses from your Nodes for an extended period of time and will have logged them both off at its end.
(Since almost forever, most log-in sessions on computers get terminated after an extended period of inactivity. This is referred to being 'timed out'.)
If this is the case then it would explain what you're experiencing.
Just a little theorising before a Sunday dinner of roast pork and loads of veg plus some stuffing (noun not verb).