Requote Storm Diagnoser

"I keep getting requoted" can mean two entirely different things that need two entirely different fixes. Either the price is genuinely moving fast enough between decision and execution that a tight deviation/slippage setting keeps rejecting the fill (fixable by widening it), or quotes themselves are arriving late or in bursts from the broker's feed, which no client-side slippage setting can fix at all. Trading forums are full of people widening deviation to fight a problem that was never about deviation. This script separates the two by sampling live ticks for a chosen window and recording, per server hour: how many ticks arrived, how many tick-to-tick price jumps crossed a "fast move" pip threshold, how many gaps between ticks crossed a "stale gap" second threshold, and the worst case of each. At the end it writes a per-hour table plus a verdict: if fast moves dominate, it names a slippage-tolerance problem; if stale gaps dominate, it names a quote-delivery/throttling problem; if both are similar, it says so and points at the specific hour to look at. It deliberately does not place live test orders to count real requotes directly - repeatedly sending orders on a live account purely to measure how often they get rejected risks real fills and real money, which is not an acceptable price for a diagnostic tool. Tick-arrival timing and tick-to-tick price movement are an honest, risk-free proxy for the same two underlying mechanisms and are stated as a proxy, not presented as an exact requote count. Notes and limitations This is a proxy diagnostic, not a direct requote counter. It cannot see the broker's actual requote decisions, only the tick feed the terminal receives - a broker could in principle requote for reasons unrelated to either fast price movement or feed timing (server-side dealing desk policy, for instance), which this tool has no way to detect. Sampling only covers the window it is actually run during; a problem that only shows up during a specific news release or session overlap needs the script running across that exact window to be caught, not a random 15-minute sample. The script must stay running (chart open, not removed) for the whole sample window - closing the chart or removing the script ends the sample early and produces a report only from ticks observed so far. Fast-move and stale-gap thresholds are fixed pip/second cutoffs the user sets, not adaptive - a symbol with naturally wide normal-condition movement (metals, indices) needs a correspondingly higher InpFastMovePips than a typically calm major forex pair, or every run will report "fast movement dominant" regardless of any real problem.

Script · MT5 · v1.0 · Free

Tags: Alerts · MT5 Script · MQL5 Source Code

MQL4 & MQL5 scripts · PolyMaria