· None of the above quite fits
· App interface looks or behaves oddly
· Clicking on band info glitches Roon Server then says not available
· TP-Link Deco BE11000
Hello @Quicksilver
Thanks for the screenshot. We tried the same thing here, the same album and the same artist page, on our own system, and it behaved normally. So this is not something about that release or its metadata, it is something specific to your setup.
One thing in your screenshot is worth looking at first. There is a red warning triangle in the toolbar at the top of your screen, next to the bookmark and search icons. That is Roon telling you something is wrong, and it is already showing before anything glitches. Please click it and tell us exactly what it says, or send a screenshot of it.
Alongside that, we still need three things to look at this properly:
The exact time. Please make it happen once more and note the date, the time and your timezone, then post that here the same day. Our logs only cover a limited window, so a timestamp sent later usually arrives too late. With it we can see whether Roon Server actually restarted or whether only the app was affected.
A short screen recording. From just before you click through to the point the message appears. That shows us the order things happen in, which a screenshot cannot. You can upload it here:
https://workdrive.zohoexternal.com/collection/nqcgjac23027d90a441bda2c314de49d7958a/external
The exact wording of the message you see when it says not available.
Please also tell us what your Roon Server runs on, and which device you are using as a remote when it happens.
The red warning triangle is backup failed. I uploaded a recording of the screen. That occurs after I click on the band name, “Ceremony”. It’s the only time I’ve encountered this with thousands and thousands of band name clicks. It is time stamped as to the time of occurrence. 8:29 PM Eastern Time. Running Roon ROCK on an Intel based Mini PC. It’s Roon on a MacBook Pro. Version 2.71 (build 1683) on both Remote and Server. Thanks.
Hello @Quicksilver
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
Hi @Quicksilver
The team is still investigating a few possibilities here, and as soon as that investigation is complete, we’ll follow up as soon as we can.
You have our apologies for the trouble here. We know this has been a tricky issue, and we’ve appreciated your patience as we continue to look into it.