After further testing, I noticed I was able to prevent this issue from happening by disabling Qobuz and leaving only TIDAL active. I wonder if this could be related to the Qobuz API issue that we are currently investigating:
I’ve forwarded your report to the team, but let’s circle back once the Qobuz issue is fully resolved and see if this still reproduces then.