Msg Parse Error: tagValue.Parse: No '=' in '\u0001' #728
Description
This error caused subsequent NewOrderSingle requests to be unable to be processed. I would like to inquire about this reason.
【Msg Parse Error: tagValue.Parse: No '=' in '\u0001', "8=FIX.4.2\x019=219\x0135=D\x0149=GG\x0156=GH\x01115=ABC\x0134=3945\x0143=Y\x0152=20250909-04:26:50.730\x01122=20250909-04:26:47.316\x0111=173794933364992\x011=15501\x0121=1\x0155=100000\x01167=CS\x01207=SS\x0154=1\x0160=20250909-04:26:47.197\x0138=100\x0140=2\x0144=18.65\x0115=CNY\x0159=0\x0177=\x01\x0110=163\x01"】
We found that the reason was that there were two separators after tag77, and there was no value. We replicated it in the testing environment. First, we sent a message with two consecutive separators at the same time, and then sent a normal NewOrderSingle message. We found that it could not be processed. Can you help us investigate what caused it? And provide solutions