correction: as the companion update is not out yet with the latency fix, also the long polling there is not yet activated. but the frontend already has it and you can already see it in the network tab in the chrome devtools. as soon as there is a message available for the frontend for the server, it will be fetched to the frontend. previously it was doing requests every 1-5 seconds, which felt sometimes slow when watching the progress bars. tomorrow we release the companion changes as well incl. the long polling and the latency fix, then it will be way more "live" than before. sorry for this, it really looks like everything is failing (when in the end everything is going even better and quicker than before). maybe we are a little bit too honest with all of our errors? our hypothesis so far is that by being aggressive with showing errors and warnings, we actually aim to build a better product by actually fixing the underlying issues and keep the pressure high on us as a development team (instead of a lot of other products than hide the errors deep in some logs)