During our integration with a Prime Broker, we encountered an issue re-establishing connections. The broker does not include OrigSendingTime (tag 122) for Admin messages, even when PossDupFlag (tag 43) is set to 'Y'. They have indicated that according to their implementation, tag 122 is only mandatory for business-level messages.
Currently, this causes a validation failure in the library, preventing the connection from recovering.
Proposed Solution:
Introduce a new configuration setting, such as allow_missing_orig_sending_time_for_admin. When enabled, the validation logic should skip the requirement for tag 122 on Admin-level messages (e.g., Heartbeats, Sequence Resets) even if tag 43 is present.
Note:
We require this fix urgently for our production environment. I will be forking the repository to implement this change and will submit a PR shortly for your review.