In order to troubleshoot this type of problem we added an „automatic restart“ in case of failures, so it does not get stuck as @Diederik described. If possible, it would be great if you could find the latest error message and send it to us. What we saw currently were some failures resulting out of our current tag browser implementation. When originally designing it, we were throwing the functionality quickly together to test if it would bring value add to the user (we now know that it is a definitive yes), so we did not think about proper architecture. In some conditions, the mgmtcompanion will not be able to catch up anymore with your tags and then the frontend will get really slow as well as the companion (up until it does an automatic restart). We are working now on this for 2 weeks and will release a fix quite soon.