{"id":7066,"date":"2025-08-28T22:35:56","date_gmt":"2025-08-29T03:35:56","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&#038;p=7066"},"modified":"2025-09-10T19:41:48","modified_gmt":"2025-09-11T00:41:48","slug":"fix-session-management","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-order-routing\/overview-tt-fix-order-routing\/fix-session-management\/","title":{"rendered":"FIX Session Management"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">TT FIX Order Routing client applications require a FIX session to be created in <strong>Setup<\/strong> in order to connect to TT FIX servers. Client applications should be designed with the following session management considerations in mind:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"#fix-session-reset-schedules\">FIX session reset schedules<\/a>\n<ul class=\"wp-block-list\">\n<li><a href=\"#sequence-number-resets\">Sequence number resets<\/a><\/li>\n\n\n\n<li><a href=\"#clordid-uniqueness\">CIOrdID uniqueness<\/a><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><a href=\"#handling-connection-problems\">Handling connection problems<\/a><\/li>\n\n\n\n<li><a href=\"#handling-missed-messages\">Handling missed messages<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"fix-session-reset-schedules\">FIX session reset schedules<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\n  TT FIX Order Routing sessions are persistent by default and reset on Saturdays\n  at 22:00 UTC.\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\n  Clients may optionally define a custom daily reset time when configuring a FIX\n  Order Routing session in Setup <a href=\"\/user-setup\/fxs-adding-and-configuring-a-fix-session.html\">Setup<\/a>.\n<\/p>\n\n\n\n<div class=\"wp-block-twentytwentyfive-child-tt-callout component-callout callout-info\"><span class=\"badge \">Note<\/span>\n<p class=\"wp-block-paragraph\">If a FIX client remains connected to a FIX session when either the default or custom scheduled reset time occurs, TT\u2019s FIX engine will send a Logout message.<\/p>\n<\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"sequence-number-resets\">On-demand sequence number resets<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">By default, message sequence numbers for FIX sessions are reset when TT resets all FIX sessions.  Message sequence numbers can also be reset, when desired, by setting Tag 34 (MsgSeqNum) = 1 and Tag 141 (ResetSeqNumFlag) = Y when sending a <a href=\"\/tt-fix\/general\/Msg_Logon_A.html\">Logon (A)<\/a> message.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"clordid-uniqueness\">ClOrdID uniqueness<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">TT FIX will ensure ClOrdID (tag 11) uniqueness for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>All orders entered since the last session reset (Saturday @ 22:00 UTC by default or per custom schedule in Setup)<\/li>\n\n\n\n<li>All GTC \/ GTDate orders entered in previous sessions that were still working at the start of the current sesssion.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For more information, refer to the <a href=\"\/tt-fix\/order-routing\/Msg_NewOrderSingle_D.html#tag11\">ClOrdID tag description<\/a> in the New Order Single (D) message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"handling-connection-problems\">Handling connection problems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\n  If your FIX client application disconnects and subsequently reconnects, TT\u2019s\n  FIX engine will perform an internal recovery process to query our cloud based\n  order book database and will deliver all unsent execution reports by applying\n  an incremental sequence number that picks up where we left off prior to the\n  disconnect. The session recovery process can be considered complete in all\n  cases with a News message [35=B].\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\n  This eliminates the requirement for your FIX client application to detect a\n  gap on the session level and request missed execution reports while\n  disconnected. This also allows FIX client applications to failover seamlessly\n  into a different datacenter without sequence number consideration.\n<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"handling-missed-messages\">Handling missed messages<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\n  If your FIX client application disconnects and was unable to process\n  executions prior to the disconnect, TT\u2019s FIX engine supports the standard\n  message replay mechanism specified by the FIX Protocol by honoring Resend\n  Request [2] messages received from FIX client applications.\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\n  In extreme cases where your FIX client application unexpectedly disconnected\n  and required intervention on your side to reset sequence numbers that resulted\n  in a subsequent Logon with 141=Y and 34=1, TT\u2019s FIX engine will still perform\n  a session recovery process that will query our cloud based order book database\n  for executions marked as undelivered and apply an incremental sequence number\n  to each message message. In this case, Logon [34=1], missed executions [34=2,\n  3, etc]. The session recovery process can be considered complete in all cases\n  with a News message [35=B].\n<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\n  In the scenario where although TT delivered all relevant execution reports to\n  your FIX client application, your internal system may have experienced an\n  issue and was unable to process the messaging. TT\u2019s FIX Engine is aware of\n  sent messages, but we are unaware of your application&#8217;s success or failure to\n  process them. If your FIX client application also required a sequence number\n  reset and cannot request a Resend Request [2] message, executions can be\n  retrieved through our REST API [link to REST].\n<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TT FIX Order Routing client applications require a FIX session to be created in Setup in order to connect to T [&hellip;]<\/p>\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[458],"class_list":["post-7066","doc","type-doc","status-publish","hentry","docs-category-overview-tt-fix-order-routing"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7066","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7066\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7066"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}