The Sequence Reset message has two modes: Gap Fill mode and Reset mode
Gap Fill mode
Gap Fill mode is used in response to a Resend Request<2> when one or more messages must be skipped over for the following reasons:
Gap Fill mode is indicated by GapFillFlag(123) field = "Y".
If the GapFillFlag(123) field is present (and equal to "Y"), the MsgSeqNum(34) should conform to standard message sequencing rules (i.e. the MsgSeqNum(34) of the Sequence Reset-GapFill<4> mode message should represent the beginning MsgSeqNum(34) in the GapFill range because the remote side is expecting that next message sequence number).
Reset mode involves specifying an arbitrarily higher new sequence number to be expected by the receiver of the Sequence Reset-Reset message, and is used to reestablish a FIX session after an unrecoverable application failure.
Reset mode is indicated by the GapFillFlag(123) field = "N" or if the field is omitted.
If the GapFillFlag(123) field is not present (or set to N), it can be assumed that the purpose of the Sequence Reset message is to recover from an out-of-sequence condition. In Sequence Reset - Reset<4> mode, the MsgSeqNum(34) in the header should be ignored (i.e. the receipt of a Sequence Reset - Reset<4> mode message with an out of sequence MsgSeqNum(34) should not generate resend requests). Sequence Reset – Reset<4> should NOT be used as a normal response to a Resend Request<2> (use Sequence Reset – Gap Fill<4> mode). The Sequence Reset – Reset<4> should ONLY be used to recover from a disaster situation which cannot be recovered via the use of Sequence Reset – Gap Fill<4>. Note that the use of Sequence Reset – Reset<4> may result in the possibility of lost messages.
Rules for processing all Sequence Reset messages
The sending application will initiate the Sequence Reset<4>. The message in all situations specifies NewSeqNo(36) to reset to as the value of the next sequence number to be expected by the message receipient immediately following the messages and/or sequence numbers being skipped.
The Sequence Reset can only increase the sequence number. If a sequence reset is received attempting to decrease the next expected sequence number the message should be rejected and treated as a serious error. It is possible to have multiple Resend Requests<2> issued in a row (e.g. 5 to 10 followed by 5 to 11). If sequence number 8, 10, and 11 represent application messages while the 5-7 and 9 represent administrative messages, the series of messages as result of the Resend Request<2> may appear as Sequence Reset-GapFill mode with NewSeqNo(36) of 8, message 8, Sequence Reset-GapFill with NewSeqNo(36) of 10, and message 10. This could then followed by Sequence Reset-GapFill with NewSeqNo(36) of 8, message 8, Sequence Reset-GapFill with NewSeqNo(36) of 10, message 10, and message 11. One must be careful to ignore the duplicate Sequence Reset-GapFill mode which is attempting to lower the next expected sequence number. This can be detected by checking to see if its MsgSeqNum(34) is less than expected. If so, the Sequence Reset-GapFill mode is a duplicate and should be discarded.
The '^' character is used to represent SOH character.