THE DEVELOPER TOOLBOX
FIX session troubleshooting
Inspect protocol messages and get a clear starting point for troubleshooting. Inputs are processed on your device.
Read a message. Trace a reject.
Choose the next check for your FIX message
- A Session Reject (35=3): paste both messages into the FIX 4.4 reject explainer to check attribution before changing a field.
- A reason number: look up the 19 SessionRejectReason (373) codes and next checks.
- A missing field or sequence mismatch: load a worked reject example to compare expected behavior.
- Business rejects, execution reports, binary payloads, or full log files: use your FIX engine, its session logs, and the counterparty specification. This toolbox does not cover those workflows.
Find the matching message in your log
Copy the reject’s RefSeqNum (45). In the outbound log for the same session and sequence reset window, find the message with that MsgSeqNum (34). Then paste the pair into the explainer to compare the references. If messages from multiple sessions are mixed together, narrow the log by sender and target IDs first.