FIX Protocol Tag 97: PossResend

Y when the message may have been sent before under a different sequence number. The receiver should check business identifiers such as ClOrdID (11) to detect a duplicate.

Tag number: 97
Data type: BOOLEAN
FIX versions: FIX 4.0 to 5.0 SP2 and FIXT 1.1
Location: Standard header

Practical notes on PossResend

PossResend = Y marks an application message sent again under a new MsgSeqNum because the sender is not sure the first copy arrived.

The session layer cannot spot this duplicate because the sequence number is new. The receiver must check business identifiers: ClOrdID (11) for orders, ExecID (17) for executions.
If the identifier is already known, the receiver should not act again; it can answer with the current state instead.

Common mistakes

Changing ClOrdID on the resend, which turns it into a second order.

Tag 97 in each FIX version

Values and message usage as defined in a specific version.

Data type

BOOLEAN: Y for yes or N for no.

Valid values

2 enumerated values across all FIX versions.

Value	Meaning
N	No
Y	Yes

Example

97=N

Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.

Decode a message with this tag

Message types that use tag 97

PossResend belongs to the standard message header, which every FIX message carries, so it is not listed against individual message types.

Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.