Page 1 of 1

When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 12:17 pm
by FXS London Scalper
One requote is a nuisance. Five in an hour, all on the same pair at busy moments, is information. Requote clusters tend to come before bigger execution problems, so it pays to have a checklist ready for when you notice them.

First, rule out your own side:
- Is your platform build current?
- Is the deviation/slippage setting on the order ticket set to zero? Some platforms requote everything outside it.
- Is your VPS or home connection showing higher ping than usual?

Then look at the broker side:
- Do requotes happen only at news, or also in quiet markets?
- Are they symmetric? If requotes appear only when price moves in your favour, that's worth documenting.
- Did anything change recently: new account type, entity transfer, server migration?

Document each requote with time (to the second), requested price, offered price and the market moment. Ten documented cases give support something specific to answer. "I keep getting requotes" gets a template reply.

If the cluster persists for a week after you've ruled out your side, it's a reasonable time to move volume to a backup account and watch whether the problem follows you.

What's the worst requote run you've had, and did the broker explain it?

Re: When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 1:47 pm
by PTScalper
Hi traders, scalpers, let's talk about execution quality today.

When you're mapping out major support and resistance zones on the H4 and D1 charts, and finally drop down to the M15 to execute a scalp, precision is everything. One requote is a nuisance. Five in an hour, all on the same pair at busy moments, is a critical piece of information. Requote clusters tend to come before bigger execution problems, so it pays to have a checklist ready for when you start noticing them.

Before pointing fingers, always rule out your own side first:

Is your platform build current? An outdated terminal can cause subtle sync issues with the trade server.

Check the deviation/slippage setting: Is the deviation setting on the order ticket set to zero? Some platforms will automatically requote everything outside of a strict zero-parameter. Give it a few points to breathe.

Check your latency: Is your VPS or home connection showing a higher ping to the broker's data center than usual?

Re: When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 1:47 pm
by PTScalper
Once your side is clean, turn your attention to the broker's side:

Market Conditions: Do requotes happen only during high-impact news events (where liquidity actually thins out), or are you getting them in quiet markets? The latter is a massive red flag.

Asymmetry: Are the requotes symmetric? If requotes only appear when the price jumps in your favor, but slippage is instantly passed through when it moves against you, that is absolutely worth documenting. That's often a sign of aggressive B-book profiling.

Infrastructure Changes: Did anything change recently? Think about new account types, entity transfers, or server migrations.

Re: When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 1:47 pm
by PTScalper
You have to document each requote with the exact time (to the second), your requested price, the offered price, and the market moment. Ten documented cases give a broker's support desk something specific to investigate. Simply complaining, "I keep getting requotes," will only get you a template reply from a Tier 1 support rep.

If the cluster persists for a week after you've ruled out your own setup, itโ€™s a reasonable time to move your volume to a backup account and watch whether the problem follows you. I personally route my capital through IC Markets because I need that consistent classic spot execution without arbitrary rules, plus the safety net of zero negative balance protection, but whatever your backup is, use it to A/B test the execution.

Re: When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 1:48 pm
by PTScalper
The Solution: Automated Background Logging

Since I execute about 99% of my trades directly from my phone, I can't easily screenshot every execution delay. Instead, I keep a lightweight MQL5 utility running in the background on my VPS terminal. It listens to the trade server and writes a hard log of any rejected orders, requotes, or price changes, capturing the exact data you need for support tickets.

You can drop this script onto any chart on your VPS, and it will silently monitor your account:

Code: Select all

//+------------------------------------------------------------------+
//|                                           Execution_Logger.mq5   |
//|                    Monitors and logs requotes and price changes  |
//+------------------------------------------------------------------+
#property copyright "PTScalper"
#property version   "1.00"
#property description "Background utility to log Requotes and Price Changes for support documentation."

//+------------------------------------------------------------------+
//| Expert initialization function                                   |
//+------------------------------------------------------------------+
int OnInit()
  {
   Print("Execution Logger initialized. Monitoring for requotes...");
   return(INIT_SUCCEEDED);
  }

//+------------------------------------------------------------------+
//| TradeTransaction function                                        |
//+------------------------------------------------------------------+
void OnTradeTransaction(const MqlTradeTransaction& trans,
                        const MqlTradeRequest& request,
                        const MqlTradeResult& result)
  {
   // We are only interested in rejected requests from the server
   if(trans.type == TRADE_TRANSACTION_REQUEST)
     {
      // 10004 = TRADE_RETCODE_REQUOTE
      // 10009 = TRADE_RETCODE_PRICE_CHANGED
      if(result.retcode == 10004 || result.retcode == 10009)
        {
         string timeStr = TimeToString(TimeCurrent(), TIME_DATE|TIME_SECONDS);
         string actionStr = (request.action == TRADE_ACTION_DEAL) ? "MARKET_ORDER" : "PENDING_ORDER";
         
         // Format the offered price based on standard Bid/Ask depending on order type
         double offeredPrice = (request.type == ORDER_TYPE_BUY) ? result.ask : result.bid;
         
         string logMsg = StringFormat("REQUOTE DETECTED | Time: %s | Symbol: %s | Type: %s | Req Price: %.*f | Offered: %.*f | Code: %d",
                                      timeStr, 
                                      request.symbol, 
                                      actionStr,
                                      _Digits, request.price, 
                                      _Digits, offeredPrice, 
                                      result.retcode);
                                      
         // Print to Journal (can be exported easily)
         Print(logMsg);
         
         // Optional: Write to a CSV file for easy attachment to support tickets
         int fileHandle = FileOpen("Requote_Log.csv", FILE_WRITE|FILE_READ|FILE_CSV|FILE_ANSI, ",");
         if(fileHandle != INVALID_HANDLE)
           {
            FileSeek(fileHandle, 0, SEEK_END);
            FileWrite(fileHandle, timeStr, request.symbol, actionStr, DoubleToString(request.price, _Digits), DoubleToString(offeredPrice, _Digits), IntegerToString(result.retcode));
            FileClose(fileHandle);
           }
        }
     }
  }

Re: When requotes start clustering: a broker health checklist

Posted: Wed Oct 21, 2026 1:48 pm
by PTScalper
Load this up, and let the VPS do the heavy lifting while you trade.

What's the worst requote run you've had recently, and did the broker actually give you a valid technical explanation for it? Let's hear your experiences below.

Re: When requotes start clustering: a broker health checklist

Posted: Thu Oct 29, 2026 6:56 pm
by FXS Prop Desk
PTScalper, logging rejections and requotes from the trade server on a VPS is a strong solution, since screenshots only catch the incidents you happen to notice. With a few weeks of such a log, clustering becomes visible: are requotes concentrated around news, around the rollover, or spread through the day? Each pattern points to a different cause, and only the last one really points at the broker.

Re: When requotes start clustering: a broker health checklist

Posted: Thu Oct 29, 2026 9:30 pm
by GrahamW1972
PTScalper my worst run was a couple of years back, about a dozen requotes on cable in one morning, and i was fully ready to blame the broker. sent support a stroppy email and got the usual template back about "volatile market conditions"... which i didnt buy because it was dead quiet. turned out id reinstalled the terminal the weekend before and the deviation had reset to zero, so teh whole thing was my own doing, bloody embarrassing. set it to a few points and the requotes vanished, never heard owt from the broker again. kept me quieter than Leeds in the second half anyway ๐Ÿ™‚