Advertisement IC Markets

Order reject and requote rates: what to log before blaming your edge

Discuss 1-minute to 15-minute price action setups, fading intraday momentum, key support/resistance zones, and proven short-term trading methodologies.
LondonScalper
Posts: 965
Joined: Sat Sep 05, 2026 7:54 am

Re: Order reject and requote rates: what to log before blaming your edge

Post by LondonScalper »

The 3-in-5 rule is roughly where I ended up, though I count it per symbol and per order type. Three rejects on market orders in five minutes means something different from three on limit modifications, which some bridges bounce for reasons unrelated to liquidity.

The latency trigger I like in principle, but a jump from 50 ms to 500 ms is one you'd notice anyway because the platform starts to feel sticky. Mine is relative: two consecutive orders at more than three times my session median. That catches the milder degradation that still costs a fraction of a pip per fill.

The spam-click lockout is the most useful of the three for me, and I'd call the threshold generous. Two requests inside 1.5 seconds on one symbol is nearly always me chasing, not the venue failing. I'd also stretch the lockout past sixty seconds. A minute is barely enough to stop the hand; the reasoning behind the chase takes longer to cool.
Recommended broker for automated trading & scalping IC Markets
LondonNewsTrader
Posts: 421
Joined: Mon Sep 21, 2026 9:30 am

Re: Order reject and requote rates: what to log before blaming your edge

Post by LondonNewsTrader »

PTScalper wrote: If you see RateLimit flags clustered heavily around rapid news events (e.g., FOMC, NFP), it means your finger is faster than the broker's FIX gateway configuration allows.
For most retail setups I'd read that cluster differently. A trader clicking by hand is unlikely to hit a gateway limit; what clusters around FOMC and payrolls is usually off quotes, requotes and price-changed rejections, because liquidity providers widen or withdraw their prices for a few seconds. Those belong in the venue column, but they aren't the same failure as a rate limit, and lumping them together hides the useful information. I'd keep the error codes separate and add a column with the number of seconds from the nearest scheduled release.

That column also tells you how to read the latency finding. If orders above 400 ms are concentrated in the minute after a release, the latency is a symptom of the market, not of your connection, and tightening timeouts won't help much.

Filtering out trader errors first is a good discipline. The NoMoney example is exactly the kind of thing that gets blamed on the broker.
FXS Prop Desk
Posts: 1689
Joined: Wed Oct 07, 2026 9:52 am

Re: Order reject and requote rates: what to log before blaming your edge

Post by FXS Prop Desk »

Monitoring latency and slippage as separate vectors is a good structure. A practical note for anyone implementing it: define the baseline per session, not globally. Latency and slippage around rollover are normally worse than during London, so a global threshold will either trigger too often in quiet hours or too late in busy ones. Rolling medians per hour avoid both problems.

It would also be useful to log how often the breaker trips and what happened to the market afterwards, to check whether the thresholds are set correctly or too sensitive.
FXS Official Team | The Idea Lab & Strategy
Post Reply