Duplicate Signal Filter: Exact Matching Rules
TeleFxBridge checks a newly parsed signal against your recent signals before execution. The current rule suppresses close matches within 10 minutes; this page documents what it does and what it does not do.
10-minute comparison window
A new signal is compared with recent signals belonging to the same TeleFxBridge user.
Direction and raw symbol
The trade direction and parsed raw symbol must match before a signal can be classified as a duplicate.
Entry proximity
When both signals include entry prices, their relative entry difference must be below 0.2%.
Documented limitations
The current rule is user-wide, not provider-specific, and is not a normalized message-content hash.
How current duplicate suppression works
For each newly parsed trade signal, the backend looks at that user's recent signals from the preceding 10 minutes. It then compares direction and the raw parsed symbol.
If both signals contain entries, the relative difference must be below 0.002, or 0.2%, for the new signal to be treated as a duplicate. This accommodates small entry differences while avoiding a claim of exact message fingerprinting.
The present comparison is user-wide rather than isolated per Telegram provider. Similar signals from two channels may therefore be suppressed when they satisfy the same matching conditions. Signals outside the 10-minute window are not caught by this rule.
Treat duplicate filtering as a useful execution safeguard, not proof that every edit, repost or semantically equivalent message will be detected. Review signal history and test the channel formats you intend to use.
How TeleFxBridge handles this end to end
Parse the new signal
The system extracts direction, raw symbol and entry values where available.
Load recent user signals
The comparison window covers the preceding 10 minutes.
Apply matching rules
Direction and raw symbol must match; available entries must be within 0.2%.
Suppress the close match
A matching new signal is classified as a duplicate before normal execution.
Frequently asked questions
What is the current duplicate window?▾
10 minutes. This is the implemented backend window, not a configurable 60-minute promise.
Is matching isolated per Telegram channel?▾
No. The current lookup is user-wide, so close signals from different providers can match.
Does it hash normalized message content?▾
No. The current rule uses direction, raw symbol and entry proximity when entries are present.
Can it detect every edited or reposted signal?▾
No. Different symbols, directions, sufficiently different entries or signals outside the window will not match this rule.
Should I still monitor copied signals?▾
Yes. Deduplication is one safeguard and should be validated with the formats used by your channels.
Related guides
Ready to automate your Telegram signals?
7-day free trial. No credit card. Test the complete workflow on a demo account first.
Start Free Trial