We have recently deployed to a staging environment (AWS, Kubernetes) and at one point while manually testing the app, there occurred an issue that I’ve never experienced before or after.
Namely, after playing a while with the app by switching (clicking) from one app context to another each comprised of a parent LV and 2 child LV processes, one of the nested LiveView instances just rendered statically without ever connecting to the server. There were no exceptions or errors and the instance did not restart by itself. After refreshing the browser it was all business as usual again and so far we have never managed to reproduce the issue.
I am aware there could be a myriad of underlying factors and that I am not providing any config details, but I simply need to know if someone else has had a similar experience and, more specifically, if someone is aware under which circumstances it is possible that a (nested) LiveVIew instance does not connect to the server and stays that way without crashing.
Thanks
