Logon (35=A) Message (Alternative Method) Instead of sending the Recovery Request (U2) message, you can also perform a Recovery Request using the Logon (35=A) message. You will similarly receive all valid messages within the specified timeframe. This method allows you to forgo sending the Recovery Request (35=U2) message; however, it is subject to your application’s […]
Reconciliation Using Custom Tag 18002 (Optional) If you need to reconcile missed messages, you can include CustomTag (18002=Y) on your Recovery Request (U2) or Logon (A) message. In doing so, FIX will search all messages from the beginning of the session (last session reset time) up to the most recent message and will send only […]
Recovery Request (35=U2) Message Method To perform a FIX Recovery using the Recovery Request (35=2) message: Log on Submit Recovery Request Receive recovered messages Get automatically logged out Note Optionally, Reconciliation can also be used. Example: Recovery Request (35=U2) Message Method An example of a FIX client sending a Recovery Request (35=U2) message to request […]