Two MT5 orders from one Telegram message are not always duplicates. Entry layers and separate take-profit orders can intentionally create several orders. A repeated message or uncertain retry is a different problem. Identify which case occurred before changing settings or resending the signal.
Updated 10 October 2026.
First, establish what the profile requested
Review the receiving account's entry mode, enabled layers and TP slots. Several entry prices can each have multiple enabled TP orders. Compare the order count, volumes and prices with those saved settings; do not assume that one Telegram message should always produce one position.
Also distinguish orders and deals from positions. MT5 netting and hedging accounts represent exposure differently. An increasing position volume can reflect multiple executions even when the terminal shows only one position for a symbol.
Trace the message before retrying
Pause the affected source's copying while you investigate unwanted new entries. Inspect existing positions and pending orders; pausing new intake does not close them.
- Check whether the provider posted once, reposted or forwarded the same idea into another selected channel.
- In Logs, filter by source and account. Compare received times, parsed values, routing results and any ticket identifiers.
- Review MT5 Experts, Journal and account history. Determine whether there were several broker-confirmed orders or repeated delivery attempts for one instruction.
- Check whether another copier or an additional execution route is also trading that account.
If the outcome remains uncertain, retain the relevant log references before asking support. Avoid reposting the signal as a diagnostic shortcut: it can add another valid instruction.
What “Avoid duplicate signals” actually checks
The setting skips repeated messages from the same channel whose parsed symbol, direction, entry, SL and TPs match within the configured duplicate window. The window is measured in seconds. Explicit re-entry instructions remain allowed.
For example, with protection enabled and a 120-second window, an otherwise matching repost after one minute can be suppressed. This is a configuration example, not a recommended window for every provider.
The setting does not promise to merge matching posts across different channels, or messages whose parsed trade values changed. A broad filter that blocks every second buy on the same symbol could also block a legitimate new setup.
Signal repeats and command retries are separate
The delivery layer also uses command identity, acknowledgements and receiver checks for retries. Those controls address replay of an instruction after a communication problem; they serve a different purpose from the same-channel signal window. Read the delivery and retry engineering guide for that distinction.
Verify the correction on demo
Use a controlled source and demo account to check one original message, one matching repost and an intentionally new setup. Compare Logs and broker results with the expected behavior. Keep layer and TP-order settings documented using the automation planning checklist. Duplicate protection reduces particular repeat scenarios; configuration errors and ambiguous outcomes still need investigation.