# Websocket connection closed - Message Too Big

**URL:** <https://forum.inductiveautomation.com/t/websocket-connection-closed-message-too-big/104761>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 7, 2025, 4:42am UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-message-too-big/104761 "2025-04-07T04:42:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [April 7, 2025, 4:42am UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-message-too-big/104761/1 "2025-04-07T04:42:42Z")

</div>

> store.Channel: Websocket connection closed. code=1009, wasClean=false, reason=Text message size [2266545] exceeds maximum size [2097152], codeMeaning=Message Too Big, codeDescription=The endpoint is terminating the connection because a data frame was received that is too large.

I've just imported a new project into a customer's existing gateway, and i'm getting this error produced by the web browser, and the client connection dies (user interaction dies since the gw has dropped the session).

I have narrowed it down to happening when I open a device popup _which contains a filtered Alarm Status Table_. If I remove the AST, then the issue goes away... Even the Designer browser briefly d/c when I open the View with the AST on it, however at least the Designer reconnects again; the client doesn't.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 7, 2025, 11:37am UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-message-too-big/104761/2 "2025-04-07T11:37:14Z")

</div>

Go through the view and make sure every property that can be made private is private. (Not certain if that will be enough. You might need to boost that max msg size.)

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [April 7, 2025, 1:31pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-closed-message-too-big/104761/3 "2025-04-07T13:31:30Z")

</div>

It turns out I had nonchalantly set `props.filters.active.results.enabled` to True, and turns out that's a really bad idea 🙂 the funny thing is, all I was needing was the length of the dataset

I've been also meaning to set more props to private though since I saw your other post not to long ago about it 👍 cheers!