Especially, when a session has expired or the server is temporarily unreachable, and/or the issue is most likely not with Jedox itself! The screenshots' alleged "critical error messages" are reactions to an "expected system behavior".
Today, the error messages could suggest - at least for non-technical people- some of their data might be missing, or even have gotten corrupted. Whereas the issue might simply be a little WLAN hiccup, not at all related to the state of the Jedox system.
Therefore, my first priority would be the login/session error handling, not just for demo purposes, but for regular users as well.
In this case, it would be great if you could 1. put some kind of reconnect attempts in there,
and at least 2. not immediately get a cascade of mainly red (X) error messages with frightening texts. Rather a friendly hint, which usual reasons the situation could have, why the server is not reachable.