Telegram Copier Risk Controls: What Is Actually Enforced

Risk settings only matter when the execution path enforces them. This page separates current server controls, current EA controls and settings that are visible but not yet enforced by the supplied EA source.

Start Free Trial — 7 DaysWatch Demo

Emergency stop

The backend blocks new pending-signal delivery while emergency stop is active.

Spread and open trades

Current MT4/MT5 sources check maximum spread and open-position/order count.

Schedule and sizing

Current EAs enforce allowed day/hour values and fixed or stop-based percentage sizing.

Known enforcement gap

Daily-loss and drawdown values exist in settings/API but are not currently enforced in the supplied EA source.

Current enforcement matrix

Verified against the current backend and supplied MT4/MT5 EA source—not a roadmap promise.

Emergency stopServer enforcedThe pending-signal API returns no new signals while emergency stop is active.
Maximum open tradesEA enforcedThe current MT4 and MT5 sources check open positions/orders before placement.
Maximum spreadEA enforcedThe current EAs compare live symbol spread with the configured points limit.
Trading day and hoursEA enforcedAllowed weekday and hour values are sent with each eligible signal batch.
Fixed lot / risk percentEA enforcedCurrent EAs support fixed sizing and stop-distance-based percentage sizing.
Daily loss / drawdownNot yet EA-enforcedSettings exist in the dashboard and API, but the supplied EA source does not currently enforce them.

Do not rely on TeleFxBridge as the sole protection for a prop-firm or live account. Broker-side limits, stop losses and independent monitoring remain necessary.

Use controls as layers, not guarantees

The backend evaluates whether a subscription and account may receive signals and can stop all new pending-signal delivery through Emergency Stop.

The current EA source applies symbol resolution, spread, open-trade count, allowed schedule and position sizing before order placement.

Daily-loss and drawdown settings must not be advertised as hard EA protection until EA enforcement is implemented, compiled, distributed and tested. Existing open positions can also move beyond any pre-trade threshold.

Use broker-side stops, conservative size, demo validation and independent monitoring. TeleFxBridge is one layer of an execution process, not an account-loss guarantee.

How TeleFxBridge handles this end to end

01

Review the matrix

Use only controls marked currently enforced.

02

Configure small sizing

Validate fixed lot or stop-based sizing against broker contract data.

03

Test each rejection

Create demo cases for spread, schedule and open-trade limits.

04

Keep independent safeguards

Use broker stops and external monitoring for account-level limits.

Frequently asked questions

Is Emergency Stop enforced?▾

Yes. The backend stops returning new pending signals while it is active. Existing open positions are not closed.

Are maximum spread and open trades enforced?▾

They are checked in the current supplied MT4 and MT5 EA source before placement.

Are daily loss and drawdown currently enforced by the EA?▾

No. Settings and API fields exist, but the supplied EA source does not currently parse and enforce them.

Does risk-percent sizing guarantee exact loss?▾

No. It estimates size from balance, entry, stop and broker tick data. Gaps, slippage and contract details can change realized loss.

Can these controls guarantee prop-firm compliance?▾

No. Firm rules vary, existing positions remain exposed and some dashboard controls have a known enforcement gap.

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