Copying delayed or slow
- Compare master event time and receiver execution time in Logs before assuming the delay is extreme.
- Home PCs and overloaded VPS setups often introduce extra delay.
- Large numbers of simultaneous connections or aggressive modify traffic can make delays worse.
Duplicate or repeated orders
- Check whether two connections target the same receiver for the same strategy.
- If using TradingView or Telegram, make sure the source itself is not sending repeated events.
- One test signal should produce one receiver order. Use that as your baseline test.
Requotes, off quotes, and price changed errors
- These are more common during fast markets, news, rollover, and thin sessions.
- Retest on a highly liquid symbol during normal hours.
- If the receiver has poor connectivity or stale prices, execution quality drops quickly.
Timeouts and rate limits
- Timeouts usually mean the receiver platform did not respond in time.
- Rate-limit and too-many-requests errors usually mean you are sending more actions than the receiver broker or platform wants to handle.
- Reduce load by closing unused terminals, easing aggressive trailing behavior, and lowering the number of simultaneous connections during testing.
Best current fix path
- Retest on one liquid symbol with one tiny trade.
- Reduce environment load. Close unused apps, terminals, or charts if the machine is overloaded.
- Reduce event spam. Aggressive SL or TP modifications, overlapping sources, and chatty webhook setups can all increase failure rate.
- Use a better environment. If you are on a local PC with latency, a cleaner Windows VPS closer to the broker often improves consistency.