READ THE MESSAGE. UNDERSTAND THE REJECT.

FIX 4.4 Session Reject Explainer

Read FIX tag=value fields, look up reason tag 373 and check whether a FIX 4.4 Session Reject (35=3) points to the message you supplied. Paste one original message and its reject response. Free, with no account.

Look up FIX tag 373 · Try troubleshooting examples

Your FIX messages

Accepts SOH, pipes (|), literal \x01 or \u0001, ^A, or one tag=value per line. Remove log prefixes. Maximum 100,000 characters per input. Inputs stay in this tab and are not uploaded or saved.

Maximum 1,000 fields per message to keep parsing and field tables responsive. Use your FIX engine for larger messages.

Loading tool…

How to investigate a FIX reject

  1. Paste one original tag=value message. Use the optional example to see a price-format rejection.
  2. Paste the counterparty’s FIX 4.4 Session Reject (MsgType 35=3). Leave it blank to read fields only.
  3. Check the reference result first: RefSeqNum (45) should match the original MsgSeqNum (34); sender and target should reverse. RefMsgType (372), when supplied, should match the original MsgType (35).
  4. Read SessionRejectReason (373), RefTagID (371), and the counterparty’s Text (58). A matching reference marks all occurrences of the referenced tag. A missing field is reported as absent.
  5. Copy the summary with its rule links, or download an ordered field array as JSON. Confirm any correction using your FIX engine and the counterparty specification.

Three reproducible reject examples

These synthetic messages have BodyLength and CheckSum calculated using ASCII bytes and SOH delimiters; pipes are displayed for readability. They illustrate troubleshooting and must not be sent to a trading system. The parser itself does not validate wire framing.

Incorrect price format · 373=6

44=oops is not numeric. The response references sequence 42 and tag 44. Inspect the highlighted Price field; a numeric representation such as 44=125.50 illustrates the expected format, not an approved order price.

Required Symbol missing · 373=1

The original omits tag 55. A matching reject points to an absent field, so there is no row to highlight. Check the message requirements before adding Symbol.

Wrong sequence reference · 45=41

The original sequence is 42 but the reject references 41. Attribution fails and the tool suppresses highlighting. Find the original message for sequence 41 before acting on the reported error.

FIX 4.4 SessionRejectReason (373) codes

These are the standard reported reasons, not diagnoses independently established by this tool. First check RefSeqNum (45), reversed CompIDs, and RefMsgType (372). Then use RefTagID (371), Text (58), and the counterparty specification to narrow the next check.

FIX 4.4 reason codes and next checks · OnixS dictionary source
373Reported reasonNext check
0Invalid tag numberCheck the tag number against the FIX 4.4 dictionary and the counterparty specification.
1Required tag missingSupply the referenced required field in the correct message or group.
2Tag not defined for this message typeCheck whether the field belongs to this message type and component.
3Undefined tagCheck the standard dictionary and any agreed custom fields.
4Tag specified without a valueSupply a value; an empty tag=value field is not a valid substitute.
5Value is incorrect (out of range) for this tagCheck the allowed enum or value range for the referenced field.
6Incorrect data format for valueCheck the field type, timestamp format, and numeric representation.
7Decryption problemCheck the agreed encryption settings with the session operator.
8Signature problemCheck the signature and agreed signing setup with the session operator.
9CompID problemCheck SenderCompID, TargetCompID, and the agreed session identity.
10SendingTime accuracy problemCheck clock synchronization and the counterparty time tolerance.
11Invalid MsgTypeCheck MsgType against FIX 4.4 and the supported counterparty messages.
12XML Validation errorInspect XML payload requirements with the counterparty.
13Tag appears more than onceCheck duplicate fields in their message or repeating-group context.
14Tag specified out of required orderCheck header, trailer, and component field ordering.
15Repeating group fields out of orderCheck the delimiter field and field order of each group entry.
16Incorrect NumInGroup count for repeating groupCompare the declared group count with the actual group entries.
17Non "Data" value includes field delimiter (SOH character)Remove the delimiter from the ordinary field value; inspect the original wire bytes.
99OtherRead Text (58) and consult the counterparty rules for the reported issue.

What the parser can establish

It splits supported text into tag, name, and value rows, keeping duplicate tags and their order. For example, multiple PartyID (448) values remain separate in JSON rather than overwriting each other. It does not reconstruct or validate repeating groups. Common tag names are supplied as a reading aid, not a complete dictionary. The original message can be read without a reject, but reason explanations and reference comparisons support FIX 4.4 Session Rejects only.

What the reference check means

A match means the supplied reference fields are consistent. It does not prove that the two messages belong to the same session: sub-IDs, qualifiers, historical messages, and sequence resets are not checked. Missing or duplicated correlation fields prevent confirmation. Mismatched or incomplete references do not highlight an original field as the confirmed target of the reject.

FIX parser questions

Does this validate BodyLength or CheckSum?

No. This version does not verify tag 9 or tag 10. Copied log text may replace SOH delimiters or change encoding; byte-level validation requires the original wire bytes. A successful split is never labelled a valid FIX message.

Can I parse binary data, entire logs, or custom dictionaries?

No. Paste a single message per box. Length-delimited Data fields, binary or encoded payloads, log prefixes, mixed delimiters, and complete log files are outside this version. Unsupported Data tags are rejected because their values can contain delimiters. Unknown custom tags are preserved without guessing their definitions.

Is a Session Reject the same as a rejected order?

No. Session Reject (35=3) reports a session-level protocol issue. BusinessMessageReject (35=j), Logout (35=5), and rejected ExecutionReports (35=8) require different rules and are not explained here.

Are messages uploaded or remembered?

No. Parsing runs in your browser without a message-processing service or browser storage. Clear messages or reload to remove the current inputs. Copy and download controls create outputs only when you use them; review the contents before sharing.

Rule sources

Field meanings and reason codes follow the FIX 4.4 Session Reject dictionary and SessionRejectReason (373) enumeration published by OnixS. Also see RefTagID (371) and RefSeqNum (45). Your agreed counterparty rules remain necessary for operational troubleshooting.