# Websocket connection closed unexpectedly **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 17, 2024, 12:43pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-unexpectedly/91944 "2024-06-17T12:43:36Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\ **Post date:** [June 19, 2024, 1:57pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-unexpectedly/91944/6 "2024-06-19T13:57:33Z")
This topic is similar to > [@Websocket max message size exceeded in Perspective when lots of alarms in Alarm Status Table](https://forum.inductiveautomation.com/t/websocket-max-message-size-exceeded-in-perspective-when-lots-of-alarms-in-alarm-status-table/78095): > > I'm building a Perspective screen with an alarm status table for a large system with lots of alarms. I am simulating the devices for now using the built-in device simulator in Ignition so a lot of alarms are triggered at the same time. When the alarms come in, I get a "Lost Connection to gateway" message in the designer and in the perspective client. The error message is below: I found a post for a similar issue, but am wondering if there is some way to optimize the alarm status tabl… The alarm status table had about 1000 unacknowledged alarms. The issue cleared up after acknowledging them. It took some time as I kept losing the connection, but it improved as more and more alarms were acknowledged. Another note on this, it also happened on views that didn't include the alarm status table, just some alarm counts in a view header (query driven). --- _[View the full topic](https://forum.inductiveautomation.com/t/websocket-connection-closed-unexpectedly/91944)._