# Error when trying to read custom device tags

**URL:** <https://forum.inductiveautomation.com/t/error-when-trying-to-read-custom-device-tags/110948>\
**Category:** Module Development\
**Tags:** ignition83\
**Created:** [September 24, 2025, 11:06pm UTC](https://forum.inductiveautomation.com/t/error-when-trying-to-read-custom-device-tags/110948 "2025-09-24T23:06:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [September 24, 2025, 11:22pm UTC](https://forum.inductiveautomation.com/t/error-when-trying-to-read-custom-device-tags/110948/2 "2025-09-24T23:22:59Z")

</div>

You can set `-Dignition.designer.websocketMaxBinaryMessageSize=4096` (default value is `2048`) in your designer launcher configuration:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7a6c9cc8a8a3d60168a4ddedd57429d006d12cf0.png)

This raises the maximum message size the designer will accept, which should allow you to get past this issue for testing.

In some near future release (possibly as early as 8.3.1, potentially later) we're going to change the way large notification messages are delivered to the client/designer to help work around this issue as a stopgap.  
In some farther future release, we're going to change the way tag values are delivered to the client/designer completely to take better advantage of the new persistent websocket that's available as of 8.3.

---

_[View the full topic](https://forum.inductiveautomation.com/t/error-when-trying-to-read-custom-device-tags/110948)._