# Decoding MT5 & cTrader Journal Logs: Requotes & Off Quotes

> Perform forensic Transaction Cost Analysis (TCA) on MetaTrader 5 and Spotware cTrader client journal logs to isolate WAN ping, bridge routing, and Off Quotes.

Canonical: https://terminalledgerdesk.com/reports/decoding-mt5-ctrader-client-journal-logs-requotes-off-quotes-ms-tca
Last updated: 2026-11-14T19:50:34.087Z

**Publication:** Terminal Ledger Desk
**Category:** Mt5 Ctrader Bridge Dealer Architecture
**Published:** 2026-11-13T22:45:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

Every MetaTrader 5 MQL5/Logs/*.log file and cTrader Journal records a multi-line millisecond state trace—separating client WAN transit from Trade Server queuing, bridge rejections, and LP Off Quotes (10021).

## Key takeaways

- Subtracting MT5 "accepted" timestamp from "done" timestamp (Delta_2) isolates pure broker Bridge + LP execution latency from your personal internet ping (Delta_1).
- Off Quotes (Retcode 10021 / MT4 136) in Market Execution signals either upstream LP Last-Look rejections, stale LP tick circuit breakers, or exhausted broker NOP credit.
- True execution TCA compares Deal Price against CopyTicksRange Bid/Ask at estimated server arrival time (t_sent + 0.5 * Delta_1), separating WAN drift from bridge slippage.
- Always archive both Terminal/Logs (Journal) and MQL5/Logs (Experts), as only the Terminal Journal records low-level network and server acceptance timestamps.

## Related financial entities

- **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.
- **MetaTrader 5 Multi-Server Cluster Architecture** (MT5-CORE) — product: Enterprise 64-bit distributed client-server architecture developed by MetaQuotes Software supporting multi-asset netting and hedging execution models.
- **Spotware cTrader Open Platform Architecture** (CTRADER-CORE) — product: High-performance STP trading platform suite developed by Spotware Systems featuring direct FIX engine access, cAlgo C# algorithms, and Open APIs.

## Analysis

When an execution goes sideways during a central-bank announcement—slipping `3.8 pips` or failing with `Off Quotes`—most traders complain with screenshots of a 1-minute candlestick chart. Institutional execution desks skip candlestick charts entirely and pull the raw **`%APPDATA%\MetaQuotes\Terminal\<ID>\Logs\YYYYMMDD.log`** or **cTrader Journal JSON/text trace**! Hidden inside those three-line millisecond state transitions (`order -> accepted by server -> process in routing -> deal performed`) is an exact hardware-like breakdown separating your local ISP latency from the broker internal [LD4/NY4 liquidity bridge](/engines/liquidity-aggregation-bridge)!

## Line-by-Line Anatomy of a Three-Step MT5 Journal Execution Trace

Open a live [MT5 Terminal](/platforms/mt5-terminal-2) `Journal` tab (not the `Experts` tab!) and inspect the exact three-line timestamp sequence emitted on a Market Buy:

1. **`14:30:01.104 Trades '804192': market buy 5.00 EURUSD`**: Local terminal stamped `t_0 = .104`, encrypted the `MqlTradeRequest`, and wrote bytes into the local OS TCP socket.
2. **`14:30:01.142 Trades '804192': accepted market buy 5.00 EURUSD`**: Server validated margin/permissions and echoed `ACCEPTED` back to your terminal at `t_1 = .142` (`Delta_1 = 38 ms` — **approximating 1 full network RTT between your PC/VPS, Access Proxy, and Trade Server!**).
3. **`14:30:01.147 Trades '804192': deal #99210482 buy 5.00 EURUSD at 1.08504 done (based on order #...)` + `execution in 43.18 ms`**: Notice **`Delta_2 = t_2 - t_1 = 147 - 142 = 5 milliseconds`**! That **`5 ms` delta isolates pure upstream Bridge + Liquidity Provider execution time** completely independent of your home internet ping!

![Three-step MT5 Journal millisecond log decomposition separating Delta_1 Client WAN RTT (38ms) from Delta_2 Bridge + LP fill time (5ms)](/api/figure?type=flow&title=Forensic%20Decomposition%20of%20MT5%20Journal%20Millisecond%20Stamps&subtitle=Isolating%20Client-to-Server%20WAN%20RTT%20%28Delta_1%29%20from%20Bridge-to-LP%20Execution%20%28Delta_2%29&steps=t0%20%3D%20.104%20Send%3A%3ATerminal%20writes%20encrypted%20MqlTradeRequest%7Ct1%20%3D%20.142%20Accept%3A%3ADelta_1%20%3D%2038ms%20%28WAN%20%2B%20Access%20%2B%20Margin%20OK%29%7CBridge%20-%3E%20LP%20FIX%3A%3AXCore%2FHub%20sweeps%20LD4%20LPs%20during%20Delta_2%7Ct2%20%3D%20.147%20Done%3A%3ADelta_2%20%3D%205ms%20%28Pure%20Bridge%20%2B%20LP%20fill%20time!%29&metrics=WAN%20COMPONENT%3A%3ADelta_1%20%2838ms%29%3A%3AShrinks%20to%201ms%20on%20LD4%20VPS%7CBRIDGE%20%2B%20LP%3A%3ADelta_2%20%285ms%29%3A%3AHealthy%20STP%20%3C%2015ms%20median%7COFF%20QUOTES%20CODE%3A%3A10021%20%2F%20E136%3A%3AZero%20LP%20depth%20or%20LL%20reject%7CTICK%20AUDIT%20API%3A%3ACopyTicksRange%3A%3AMillisecond%20Bid%2FAsk%20proof)

## `Requote (10004)` vs `No Prices / Off Quotes (10021)` vs `Reject (10006)`: Root Causes

Traders routinely conflate `Requote` and `Off Quotes`, yet inside [MT5 clusters](/engines/metatrader-5-server-cluster) and [cTrader](/platforms/ctrader-terminal-97) they diagnose completely different failure layers:
- **`Requote (10004)`**: Occurs **only** in `Instant Execution` mode when price moved outside `request.deviation` before execution. Fix: switch to an ECN `Market Execution` account.
- **`No Prices / Off Quotes (10021)` (`MT4 Error 136`)**: Occurs EVEN in `Market Execution` when **zero executable upstream LP liquidity exists**! Three real engineering triggers cause `10021`: (a) **Bridge Tick Spike / Staleness Filter** tripped because all LP feeds froze `> 2,000 ms` or crossed excessively; (b) **LP Last-Look Reject Waterfall Exhausted** (`3 out of 3` LPs rejected your `IOC` sweep during NFP); or (c) **Broker Prime-of-Prime `NOP` Credit Line Full**!
- **`Request Rejected (10006)`**: Dealer rule, symbol `Close-Only` state, or pre-trade risk collar block.

| Terminal Return Code | MT4 Legacy Code | Exact Server / Bridge Meaning | Engineer / Trader Action |
| :--- | :--- | :--- | :--- |
| **`10009` (`DONE`) / `10010` (`PARTIAL`)** | `ERR_NO_ERROR (0)` | Executed completely or partially on book | Reconcile `DEAL_PRICE` vs `CopyTicksRange` |
| **`10004` (`REQUOTE`)** | `ERR_REQUOTE (138)` | Instant-mode price moved past `deviation` | Migrate to `Market Execution` ECN account ([MT5](/platforms/mt5-terminal-2)) |
| **`10021` (`NO_PRICES` / Off Quotes)** | `ERR_OFF_QUOTES (136)` | **All LPs rejected `IOC` OR quote stream stale** | Split clip size (`< 20 lots`) or avoid 0-liquidity rollover |
| **`10030` (`INVALID_FILL`)** | N/A | Wrong `ORDER_FILLING_FOK/IOC` bitmask | Query `SYMBOL_FILLING_MODE` dynamically |
| **`10019` (`NO_MONEY`)** | `ERR_NOT_ENOUGH_MONEY` | Free margin `< InitialMargin` at `t_1` | Check weekend/news dynamic leverage tier drop! |

## MT5 & cTrader Journal Error Code Forensic Mapping Matrix

Translating terminal error codes into exact server, bridge, or upstream FIX `OrdRejReason (103)` root causes.

```formula
Delta_1_WAN_ms = t_journal_accepted - t_journal_order_sent
Delta_2_Bridge_ms = t_journal_deal_done - t_journal_accepted
Slippage_True_Pts = Dir * ( Px_Tick_At(t_sent + 0.5 * Delta_1) - Px_Deal_Done ) / Point

Worked Forensic Dispute Calculation (Buy 10 Lots GBP/USD, Dir = +1):
 t_sent = .200 (Client saw Ask = 1.27500) ; t_accepted = .280 (Delta_1 = 80ms -> Order hit server @ ~.240)
 CopyTicksRange @ .240 shows Ask already moved to 1.27506 before order arrived! Deal filled @ 1.27507 (t_done = .284, Delta_2 = 4ms)
 Conclusion: 0.6 pips was pure client WAN flight delay (.200->.240); broker LD4 bridge slipped only 0.1 pips in 4 ms!
```

## cTrader Execution Timeline & FIX `Tag 58 (Text)` Transparency

Inside [Spotware cTrader](/engines/spotware-ctrader-architecture) (`Desktop` and [cTrader Web](/platforms/ctrader-web-terminal-104)), expanding any Historical Deal opens an explicit **Event Timeline** showing millisecond-precision server UTC stamps (`Submitted -> Accepted -> Filled / Partially Filled / Cancelled`) alongside exact requested price vs VWAP fill price.

Even better, when connecting via cTrader [FIX 4.4 API](/software/fix-api), rejected `ExecutionReport (35=8, 39=8)` frames populate `Text (Tag 58)` with structured rejection diagnostics (`INSUFFICIENT_FUNDS`, `MARKET_CLOSED`, `NO_LIQUIDITY`), letting automated TCA scripts separate internal margin bugs from upstream LP fades—complementing our [Virtual Dealer vs Market Execution audit](/reports/virtual-dealer-plugin-artificial-delay-vs-market-execution-audit) and [MT5, cTrader & Liquidity Bridge Architecture Guide](/reports/mt5-ctrader-liquidity-bridge-server-topology-execution-logs-guide).

![Typical Delta_2 (Accepted-to-Done) bridge execution duration across Firm LD4 CLOB, Last-Look Bank Stream, Multi-Retry Waterfall, and Virtual Dealer Hold](/api/figure?type=bars&title=Diagnosing%20Upstream%20Infrastructure%20via%20%60Delta_2%60%20%28%60t_done%20-%20t_accepted%60%29&subtitle=What%20the%20gap%20between%20%22accepted%22%20and%20%22done%22%20reveals%20about%20your%20broker%20backend&steps=Internalized%20%2F%20Firm%20LD4%20CLOB%3A%3A0.5%E2%80%934.0%20ms%20%20%20Zero%20Last-Look%20hold%7CTier-1%20Bank%20Stream%20%28Short%20LL%29%3A%3A8.0%E2%80%9335.0%20ms%20%20%20Bank%20Last-Look%20window%7CBridge%202-Hop%20Retry%20Waterfall%3A%3A45.0%E2%80%93110.0%20ms%20%20%20LP%20%231%20rejected%20-%3E%20LP%20%232%7CSuspect%20Virtual%20Dealer%20Hold%3A%3A250.0%E2%80%931%2C000%20ms%20%20%20Constant%20timer%20floor!&metrics=HEALTHY%20MEDIAN%3A%3A%3C%2015%20ms%3A%3ADelta_2%20on%20Tier-1%20ECNs%7CSTALE%20STREAM%3A%3A%3E%202%2C000%20ms%3A%3ATriggers%2010021%20Off%20Quotes%7CLOG%20LOCATION%3A%3ALogs%2F*.log%3A%3AJournal%20!%3D%20Experts%20log%20tab%7CDISPUTE%20KEY%3A%3ADeal%20%2B%20CopyTicks%3A%3AProves%20exact%20BBO%20at%20t1)

## Automating Python / MQL5 Daily Log Parsers for Best-Execution Disputes

If you ever need to file a formal execution dispute with a broker compliance desk under [UK FCA](/standards/fca) `DISP` or [NFA](/standards/nfa) rules, screenshots carry minimal weight. Submit: (1) the exact raw `YYYYMMDD.log` lines with UTC offset, (2) `Order Ticket #` and `Deal #`, (3) `CopyTicksRange(..., COPY_TICKS_ALL)` millisecond Bid/Ask array +/- `5 seconds` around `t_0`, and (4) `Delta_1` vs `Delta_2` breakdown!

Stress-test expected CPI spread widening and rejection cushions inside the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator) and explore more log diagnostics in the [MT5, cTrader & Bridge Topic Hub](/topics/mt5-ctrader-bridge-dealer-architecture).

- [Tick-Filtering Gateways: Off-Market Spike Suppression & Quote Aggregation Throttles](/reports/tick-filtering-spike-gateways-lp-price-stream-aggregation-throttles)

## Frequently asked questions

### What is the difference between the Experts tab log and the Journal tab log in MT5?

The Experts tab (MQL5/Logs) only prints output generated by your EA Print statements, whereas the Journal tab (Logs/YYYYMMDD.log) is written by the C++ terminal engine itself—recording socket handshakes, server failover pings, and multi-stage order acceptance!

### Why do Off Quotes (10021) spike every day between 23:59 and 00:05 server time (17:00 EST)?

At 17:00 New York Rollover, global Tier-1 banks reset daily settlement ledgers and temporarily pull or widen spot FX quotes for 60–180 seconds; bridge spread/staleness filters intentionally block execution (10021) rather than filling Market orders across a 15-pip vacuum!

### How can I download millisecond historical ticks inside MT5 to verify a bad fill?

Run a 5-line MQL5 script calling CopyTicksRange(_Symbol, ticksArray, COPY_TICKS_ALL, startTimeMs, endTimeMs): MT5 downloads the broker exact server-recorded millisecond Bid/Ask tick tape from the History Server so you can audit BBO at exact fill millisecond.

### Why did Delta_2 jump from 3ms normally to 65ms on a 50-lot order without a Virtual Dealer?

On large institutional tickets (30–100 lots), if top-of-book LP #1 uses a 25ms Last-Look window and rejects its slice, your bridge Retry Waterfall automatically re-routes the remaining lots to LP #2 and LP #3—legitimately adding one or two 25ms LP hops!


## Source URLs

- https://www.mql5.com/en/docs/constants/errorswarnings/enum_trade_return_codes
- https://www.mql5.com/en/docs/series/copyticksrange
- https://help.ctrader.com/ctrader/trading/orders/

## Citation

- APA: Marcus Thorne, CQF. (2026). Decoding MT5 & cTrader Client Journal Logs: Millisecond TCA, Requotes & Off Quotes. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/decoding-mt5-ctrader-client-journal-logs-requotes-off-quotes-ms-tca
- Canonical article: [Decoding MT5 & cTrader Client Journal Logs: Millisecond TCA, Requotes & Off Quotes](https://terminalledgerdesk.com/reports/decoding-mt5-ctrader-client-journal-logs-requotes-off-quotes-ms-tca)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
