FIX Protocol Tag 373: SessionRejectReason
Reason for a session-level Reject (35=3), such as required tag missing or value is incorrect.
- Tag number
- 373
- Data type
- INT
- FIX versions
- FIX 4.2 to 5.0 SP2 and FIXT 1.1
- Used in
- 1 message type
Practical notes on SessionRejectReason
SessionRejectReason gives the reason on a session-level Reject (35=3): why the message failed validation.
- Read it with RefSeqNum (45), RefMsgType (372) and RefTagID (371), which point at the message and the field.
- Most seen: 1 Required tag missing, 2 Tag not defined for this message type, 5 Value is incorrect, 6 Incorrect data format, 9 CompID problem, 10 SendingTime accuracy problem, 11 Invalid MsgType.
- The rejected message used up its sequence number. Send a corrected message as a new message.
Changes between FIX versions
- Added in FIX 4.2 with codes 0 to 11. FIX 4.3 adds 12 to 17, FIX 4.4 adds 99 (Other), and FIX 5.0 SP1 adds 18 (Invalid or unsupported application version).
See also:Required tag missing (373=1)Value is incorrect (373=5)SendingTime accuracy problem (373=10)
Tag 373 in each FIX version
Values and message usage as defined in a specific version.
Data type
INT: A whole number without a decimal point. It may be negative.
Valid values
20 enumerated values across all FIX versions.
| Value | Meaning | FIX versions |
|---|---|---|
| 0 | Invalid tag number | All |
| 1 | Required tag missing | All |
| 2 | Tag not defined for this message type | All |
| 3 | Undefined tag | All |
| 4 | Tag specified without a value | All |
| 5 | Value is incorrect | All |
| 6 | Incorrect data format for value | All |
| 7 | Decryption problem | All |
| 8 | Signature problem | All |
| 9 | CompID problem | All |
| 10 | Sending time accuracy problem | All |
| 11 | Invalid MsgType | All |
| 12 | XML validation error | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 13 | Tag appears more than once | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 14 | Tag specified out of required order | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 15 | Repeating group fields out of order | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 16 | Incorrect NumInGroup count for repeating group | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 17 | Non data value includes field delimiter | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| 18 | Invalid or unsupported application version | 5.0 SP1, 5.0 SP2 |
| 99 | Other | 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
Example
373=0
Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.
Decode a message with this tagMessage types that use tag 373
- Reject 35=3
Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.
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.