Session-Level Messages
Reject <3>
Gemini sends a Reject <3> message when a message is received but cannot be properly processed due to a session-level rule violation. A reject is typically a serious error in the trading application's session logic. A session reject would also be generated if client message rate has exceeded the allocated throttle.
FIELDS
| Tag | Name | Req | Description |
|---|---|---|---|
| Standard Header | Y | MsgType = 3 | |
| 45 | RefSeqNum | Y | MsgSeqNum <34> of the rejected message. |
| 58 | Text | N | Explanation for rejection |
| 371 | RefTagID | N | The tag number of the FIX field being referenced. |
| 372 | RefMsgType | N | The MsgType <35> of the rejected message. |
| 373 | SessionRejectReason | N | Code to identify the reason for the Reject <3> message. Valid values: 0 = Invalid tag number1 = Required tag missing2 = Tag not defined for this message type3 = Undefined Tag4 = Tag specified without a value5 = Value is incorrect (out of range) for this tag6 = Incorrect data format for value10 = SendingTime <52> accuracy problem11 = Invalid MsgType <35>99 = Other |
| Standard Trailer | Y |