Since Friday, I can't get the tag browser (classic) no longer to work. I tried a fresh install of UMH classic on a new VM, and just use historian. But no tags are showing up. I think this is since Friday? I noticed quite some updates in the mangement console UI, perhaps something went wrong with updates?

Thanks! It looks promising, the developement of Core btw. Planned to test drive this week 🙂

The initial version for our new Topic Browser page went live today (about 2h ago), thus it sounds unlikely that it is related to that. Furthermore, only the sidebar entry has been renamed for "explicitness". But, if interested, we can still confirm whether the UI is the problem or not as follows: - Open browser dev tools (F12) > Application tab > IndexedDB (under "Storage") > UNSLocationDB > locations If you see data on the right hand side (multiple row entries), then it's a UI problem. If not, the problem lies likely on the companion side because the data is not sent to the client.

Thanks for your response. I think it's a companion side issue on this specific instance. I checked at another instance and there indeed it's still up and running.

You can check if the mgmtcompanion is having trouble reading new Kafka messages, by visiting :8090 and navigating to the "Consumer Group" tab. If umh-mgmtcompanion is either not present at all, not stable or has a large lag (over a couple thousand), then a restart of the companion might help, because it seemingly lost it's kafka connection and is unable to fix it by itself. If everything looks good on the Kafka side, it would be great if you can send me the mgmtcompanion log itself, so i can take a look tomorrow. https://cdn.discordapp.com/attachments/1389213779073700051/1389281634607566908/Screenshot_2025-06-30_at_18.27.04.png?ex=68640cd9&is=6862bb59&hm=588feb8b925ed30ad3d83abfc93401908c763f350ff3bcd9fcd72ed6a5be799a&