We consulted the documentation provided on your site regarding the functionality and setup. However there is a bit of additional clarification required: All the messages received via Websocket have a Sequence number. The definition in the documentation is relatively vague: Sequence number intended to help with temporal ordering. Typically, this will be incremented with every message, but may have gaps depending on the sequencing algorithm being used. As a general approach for this protocol such a message is used so that the receiver may decide whether a received message is relevant in a given context. These messages are not guaranteed to be received in the actual sending order, therefore this Sequence number would have the role of ordering the messages in that scope. The problem that we encountered is that this Seq Number seems to be resetting to 0(zero) at any point in the day as it reaches 65535, behavior that makes the assumed functionality unusable.
How can we have a clean behavior in regard to Seq Number?