{{Quickfixn}} OrderStatusRequest issue

[xmoon 2000]

Hi,

I always receive a 35=h message from a particular server straight after logon.

I have not written any code to handle this message - I assume it is
handled by QuickFIXn automatically like a heartbeat?

Today, for the first time, this message caused a Cracker exception. On
restarting the connecting, the message did NOT generate a Cracker
exception as usual.

What might have happened to cause the message to create a Cracker exception?

This message caused exception:
20201002-00:23:51.253 : 8=FIX.4.4 9=67 35=h 49=yyy 34=2
52=20201002-00:23:51.234 56=xxxxxxx 336=0 340=2 10=181

This did not:
20201002-03:05:29.953 : 8=FIX.4.4 9=67 35=h 49=yyy 34=2
52=20201002-03:05:29.947 56=xxxxxxxt 336=0 340=2 10=200