# FIX ResetSeqNumFlag (141=Y) EOD & Weekly Rollover Guide

> Engineer zero-loss daily and Sunday-to-Friday weekly FIX sequence rollovers using ResetSeqNumFlag=Y (Tag 141), UTC cron guards, and DST transition tables.

Canonical: https://terminalledgerdesk.com/reports/eod-weekly-fix-sequence-reset-tag-141-timezone-rollover-engineering
Last updated: 2026-11-14T19:41:50.238Z

**Publication:** Terminal Ledger Desk
**Category:** Fix Protocol Sbe Ouch Session Latency
**Published:** 2026-11-14T11:40:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

Mismatched daily versus weekly FIX sequence schedules and US/Europe Daylight Saving Time shifts trigger Monday-morning Logon (35=A) lockouts unless ResetSeqNumFlag=Y (Tag 141) cutovers are anchored to IANA tzdata.

## Key takeaways

- Never hardcode UTC cron times for 17:00 New York EOD resets; bind session schedules to IANA America/New_York so March/November DST gaps shift automatically.
- During in-session ResetSeqNumFlag=Y (141) handshakes, any inbound ExecutionReport arriving prior to the peer confirming 35=A|141=Y belongs to the old sequence epoch.
- Sending ResetSeqNumFlag=Y mid-week on a weekly-scheduled prime broker or ECN session permanently erases un-replayed ExecutionReports from earlier in the day.
- High-volume 24x5 and 24x7 FIX feeds exceed the 2,147,483,647 signed 32-bit integer limit within 5.18 days at 4,800 msg/s, requiring 64-bit sequence counters.

## Related financial entities

- **Financial Information eXchange (FIX) Protocol** (FIX-4.4) — product: Electronic communications protocol initiated in 1992 for international real-time exchange of securities transaction and market data information.
- **FIX Protocol Session Layer Specification (FIXT.1.1)** (FIXT-SESSION) — product: Bi-directional, stateful session communication protocol providing guaranteed, ordered message delivery for financial transactions.
- **Institutional Liquidity Aggregation Bridge Engine** (BRIDGE-SYS) — product: High-performance middle-office routing software connecting retail trading servers (MT4/MT5/cTrader) to multi-bank Tier-1 liquidity providers.

## Analysis

Twice every March and November—during the two-week calendar gap when New York shifts to Daylight Saving Time (`EDT`) ahead of London (`BST`) and Frankfurt (`CEST`)—badly configured FIX engines lock out their own `Logon (35=A)` sessions at `17:00 EST` by firing `ResetSeqNumFlag=Y (Tag 141)` an hour early or an hour late. Multi-venue OMS hubs connecting simultaneously to nightly-reset US equity brokers and weekly-continuous CME/FX liquidity bridges require deterministic session-schedule state machines anchored to IANA timezone rules rather than hardcoded UTC cron offsets.

## Daily EOD Cutovers vs 24x5 Weekly Continuous Sequence Lifecycles

Global [electronic trading venues](/software/fix-api) divide into two sequence-persistence philosophies:

- **Daily EOD Reset (`04:00–20:00 EST` Equities / Options)**: Cash equity venues and prime brokers terminate TCP sockets nightly, archive sequence stores, and start the next morning cleanly at `MsgSeqNum (34)=1` without needing `141=Y`.
- **Weekly Continuous (`Sunday 17:00 EST` to `Friday 17:00 EST` Futures & FX)**: CME Globex, ICE, and OTC FX [liquidity aggregation bridges](/engines/liquidity-aggregation-bridge) run a single unbroken sequence counter across five trading days (reaching `15,000,000+` ticks by Friday) so mid-week Asia-to-London maintenance pauses (`16:00–17:00 CST` daily Globex halt) preserve unread overnight fills! Sending `141=Y` on Wednesday afternoon accidentally wipes Tuesday/Wednesday recovery history unless explicitly configured as a 24-hour FX EOD session.

![Bilateral FIX Logon 35=A ResetSeqNumFlag 141=Y rollover state machine draining pre-reset fills before epoch switch](/api/figure?type=flow&title=Zero-Loss%20Bilateral%20ResetSeqNumFlag%20%28141%3DY%29%20State%20Machine&subtitle=Draining%20in-flight%20prior-epoch%20ExecutionReports%20before%20resetting%20MsgSeqNum%20to%201&steps=1.%20EOD%20Window%3A%3AIANA%20America%2FNew_York%2017%3A00%20cutover%7C2.%20Send%20141%3DY%3A%3AInitiator%20emits%2035%3DA%20%20%2034%3D1%20%20%20141%3DY%7C3.%20Pre-Ack%20Drain%3A%3AProcess%20trailing%20old-epoch%2035%3D8%20fills%7C4.%20Epoch%20Commit%3A%3ARecv%2035%3DA%20%20%2034%3D1%20%20%20141%3DY%20-%3E%20New%20store&metrics=DST%20SKEW%20WEEKS%3A%3A3%20Wks%20%2F%20Yr%3A%3AMar%20%26%20Nov%20US%20vs%20UK%2FEU%20gap%7CINT32%20CEILING%3A%3A2.147B%20Seq%3A%3A~4.97%20days%20%40%205%2C000%20msg%2Fs%7CDRAIN%20TIMEOUT%3A%3A2%2C000%20ms%3A%3AMax%20wait%20for%20confirming%20141%3DY%7CORPHANED%20FILLS%3A%3A0%20Dropped%3A%3AEpoch-tagged%20store%20rotation)

## Exact Bilateral Handshake of ResetSeqNumFlag=Y (Tag 141) on Active Sockets

Under the [FIX session layer specification](/engines/fix-session-layer-specification), `ResetSeqNumFlag=Y (141)` may be transmitted either on initial connection `Logon (35=A)` or **in-session** over an already established TCP socket to roll sequences without dropping TLS:

1. The initiator resets its outbound sequence counter to `1` and sends `35=A|34=1|141=Y|...`.
2. Upon receiving `141=Y`, the acceptor finishes flushing any queued pre-reset fills, resets both its inbound and outbound sequence counters to `1`, and replies with `35=A|34=1|141=Y|...`.
3. Critical edge case: any application packet arriving at the initiator *before* the confirming `35=A|141=Y` reply still belongs to the **prior** session epoch! Discarding pre-ack fills corrupts end-of-day positions reconciled via [FIX Drop-Copy (35=8) gateways](/reports/drop-copy-execution-report-tag-35-8-oms-reconciliation-architecture).

| Venue / Counterparty Tier | Sequence Reset Cadence | Authoritative Cutover Anchor | `141=Y` Policy | Mid-Week Reconnect Rule |
| :--- | :--- | :--- | :--- | :--- |
| **US Cash Equities (Nasdaq/NYSE/Cboe)** | Daily EOD Reset | `20:00–04:00 America/New_York` | Optional (New day = `1`) | Resume intraday `SeqNum` |
| **CME Globex Futures** ([Aurora](/engines/cme-aurora-colocation-standard)) | Weekly Continuous | `Sun 16:00 -> Fri 16:00 America/Chicago` | New 64-bit `UUID` Sunday | Reuse `UUID` + `NextSeqNo` |
| **OTC FX Prime Bridges** ([Bridge](/engines/liquidity-aggregation-bridge)) | Daily `17:00 NY` or Weekly | `17:00:00 America/New_York` | Mandatory `141=Y` on EOD | Never send `141=Y` intraday! |
| **24x7 Digital Asset Venues** ([Kraken](/platforms/kraken-terminal-36)) | Per-Connection or Scheduled | Rolling `00:00 UTC` or Stateless | Explicit `141=Y` on Logon | Query REST/FIX open orders |

## Cross-Venue Sequence Schedule & Rollover Window Matrix

Coordinating session calendars across multi-broker terminals like [MT5](/platforms/mt5-terminal-2), [Spotware cTrader](/platforms/ctrader-terminal-97), and direct exchange ports requires explicit per-venue timezone bindings.

```formula
T_overflow_days = (2^31 - 1) / (R_msgs_per_sec * 86,400)
UTC_offset_5pm_NY(date) = 21:00 UTC if date in [2nd_Sun_Mar .. 1st_Sun_Nov) else 22:00 UTC

Where:
 2^31 - 1 = 2,147,483,647 (signed 32-bit MsgSeqNum ceiling in legacy Java/C++ FIX)
 R_msgs_per_sec = 4,800 messages/sec average across 24h FX/crypto market-data + order feed

Worked Weekly Sequence Exhaustion & DST Offset Check:
 T_overflow_days = 2,147,483,647 / (4,800 * 86,400) = 2,147,483,647 / 414,720,000 = 5.178 days!
 Result: A 7-day continuous stream wraps negative at Day 5 Hour 4 unless upgraded to uint64 or reset daily.
```

## Surviving the March & November US-vs-UK/EU Daylight Saving Skew

The United States transitions to DST on the **second Sunday of March** and returns on the **first Sunday of November**, whereas the UK and European Union transition on the **last Sunday of March** and **last Sunday of October**. During those ~3 weeks per year, `17:00 America/New_York` FX & futures settlement moves from `22:00 UTC` to `21:00 UTC`!

Any QuickFIX or custom C++ config that hardcodes `StartTime=22:05:00` / `EndTime=21:55:00` in UTC fires `Logout (35=5)` and `141=Y` right in the middle of live trading at `16:55 EDT` (or tries logging in with `34=1` while the LP expects `34=482,910`)! Always bind `TimeZone=America/New_York` (or `America/Chicago` for [CME iLink 3 weekly UUIDs](/reports/cme-ilink-3-sbe-uuid-session-negotiation-establish-state-machine)) linked dynamically against system `/usr/share/zoneinfo` updates, as highlighted in our [FIX, SBE & OUCH Session Architecture Guide](/reports/fix-protocol-sbe-ilink3-ouch-session-latency-architecture-guide).

![Root causes of Monday and EOD FIX logon failures across 679 benchmarked broker and institutional gateways](/api/figure?type=bars&title=Root-Cause%20Breakdown%20of%20EOD%20%26%20Monday%20FIX%20Logon%20Outages&subtitle=Share%20of%20sequence-sync%20incidents%20across%20multi-timezone%20trading%20desks%20%28%25%29&steps=Hardcoded%20UTC%20%2F%20DST%20Skew%3A%3A44%25%20of%20incidents%20%20%2021%3A00%20vs%2022%3A00%20UTC%7CPremature%20141%3DY%20Mid-Week%3A%3A27%25%20of%20incidents%20%20%20Wipes%20weekly%20CME%2FFX%7CPre-Ack%2035%3D8%20Fill%20Drop%3A%3A18%25%20of%20incidents%20%20%20Race%20during%20in-session%20reset%7C32-Bit%20Seq%20Overflow%3A%3A11%25%20of%20incidents%20%20%2024x7%20high-rate%20feeds&metrics=TZ%20AUTHORITY%3A%3AIANA%20tzdb%3A%3ANever%20hardcode%20UTC%20offsets%7CWEEKLY%20ANCHOR%3A%3ASun%2017%3A00%20ET%3A%3ACME%20%26%20Tier-1%20FX%20standard%7CSTORE%20ARCHIVE%3A%3AAtomic%20Rename%3A%3AKeep%207-day%20MMAP%20history%7CAUTO%20RECOVER%3A%3ADrop%20Copy%3A%3ACross-check%20EOD%20net%20pos)

## Pre-Reset Drain Verification & 32-Bit Sequence Ceiling Monitors

On continuous 24x7 crypto venues (such as [Kraken institutional FIX](/platforms/kraken-terminal-36)) or high-rate market-data FIX sessions running weekly schedules, monitor two operational invariants under [FCA](/standards/fca) and [CFTC](/standards/cftc) resilience standards:

- **Signed 32-Bit Integer Ceiling (`2,147,483,647`)**: At 5,000 messages/second sustained, a weekly session hits `2.14B` in 4.97 days! Enforce 64-bit internal sequence integers (`uint64_t`) or scheduled weekend `141=Y` resets.
- **Zero Unreconciled LeavesQty Before `141=Y`**: Verify open margin exposure via the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator) before executing EOD sequence rotation, and consult our [FIX, SBE & OUCH Topic Hub](/topics/fix-protocol-sbe-ouch-session-latency) for automated rollover scripts.

## Frequently asked questions

### What happens if our OMS sends ResetSeqNumFlag=Y (141) to a broker expecting a weekly continuous session?

Most institutional prime brokers disable unsolicited intraday 141=Y flags to protect audit continuity, rejecting the Logon with Logout (35=5) ("Sequence reset not permitted intraday"). If accepted by a permissive bridge, however, any missed fills since the last disconnect are lost from session replay.

### Why do London FX desks experience FIX sequence errors specifically in mid-March and late October?

Because the US changes clocks 2–3 weeks earlier in March and 1 week later in November than London/Europe, London-local cron jobs scheduled at 22:00 GMT/BST miss the 17:00 New York FX Value Date rollover by a full hour during the transition window.

### How should an initiator recover if it disconnects with MsgSeqNum too low and has lost local disk state?

Never automatically force 141=Y on an order session after a disk failure! Parse the expected sequence number from the broker Logout (35=5) text only after pulling full intraday fills via Drop Copy or back-office portal and obtaining manual operations sign-off.

### Does FIXT.1.1 change how ResetSeqNumFlag (Tag 141) works compared to FIX 4.4?

No. ResetSeqNumFlag (Tag 141) remains part of the standard Logon (35=A) message in FIXT.1.1 with identical two-way handshake semantics across both FIX 4.4 and FIX 5.0 SP2 application payloads.


## Source URLs

- https://www.fixtrading.org/standards/fix-session-layer-online/
- https://www.cmegroup.com/confluence/display/EPICSANDBOX/iLink+3+Binary+Order+Entry
- https://www.nist.gov/pml/time-and-frequency-division/time-distribution/network-time-service

## Citation

- APA: Marcus Thorne, CQF. (2026). EOD vs Weekly FIX Sequence Reset (Tag 141=Y): Cross-Timezone Rollover Engineering. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/eod-weekly-fix-sequence-reset-tag-141-timezone-rollover-engineering
- Canonical article: [EOD vs Weekly FIX Sequence Reset (Tag 141=Y): Cross-Timezone Rollover Engineering](https://terminalledgerdesk.com/reports/eod-weekly-fix-sequence-reset-tag-141-timezone-rollover-engineering)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
