Hey @Jonathan_Winer,
Thanks for the detailed follow up!
We checked numerous timestamps and observed the same pattern across each occurrence. There are repeating FTMSI-B timeouts with Qobuz, causing the file not to download in time for playback.
Your Roon Server likely had a good upstream connection initially but then lost it or it got throttled. Bandwidth regulation could be one thing, as well as interference from other devices in the network.
Yes, 5000 tracks is the max limit for shuffle, see more about that here.
My apologies here as I failed to recall this - if the device was removed from the chain and issues persisted, we can rule it out. 
However, we’re still seeing bandwidth limits being set, likely causing these issues. For example:
Trace: FTMSI-B 4 FileCache qo/A9FCD957 dwStatus:AllBlocksDownloaded files:0 accessTimeOut:True priorities: ('zoneplayer:8':485) --> bw limit:0kbps
Debug: FTMSI-B-OE qo/4A9B864E exit thread signalled
Info: FTMSI-B FileCache disposed qo/4A9B864E
Warn: [easyhttp] [11778] GET https://streaming-qobuz-std.akamaized.net/file?uid=2024821&eid=118897306&fmt=27&profile=1725397972 web exception without response: socketmsg (ConnectionRefused): Connection refused
Warn: FTMSI-B-OE qo/D55E9572 rid:1 error response: 999
Were you able to review any options to allocate additional network priority to the Nucleus from your router settings?