A carefully sized order can still belong to a carelessly configured account. Several channels may recommend the same instrument, one message may produce several target allocations, and another route may copy the same idea to an account you forgot was connected. The balance sheet adds these actions together even when the dashboard displays them separately.
Begin with the account's possible combined exposure, then work backwards to each route. Position sizing determines the requested quantity; account protection also involves concurrent positions, management behaviour and interruption handling. No single percentage is universally safe, and automation does not make a weak source profitable.
In this guide
Count what each target actually creates
Splitting one intended quantity across three targets is different from sending that full quantity to each target. In an illustrative setup, dividing 0.30 lots into three 0.10 allocations preserves the original total, while three allocations of 0.30 produce 0.90 lots. The target labels can look identical while the exposure triples.
Check the resulting orders in the destination history. The multiple-target guide explains why minimum volume and rounding can complicate even an equal split. A tidy configuration screen cannot certify the final allocation.
Several sources may express one market view
Two gold channels can react to the same move, and several currency trades can share a common currency exposure. Counting channel names is therefore a poor measure of diversification. Record the actual instruments, directions and concurrent positions rather than assuming each source contributes an independent risk.
The multi-channel guide shows routing arrangements, but routing is not an account-level exposure limit. A setting that sizes each incoming instruction cannot necessarily see or prevent the combined position you intended to cap. Verify any protective feature in current documentation before relying on it.
Stop distance is a calculation input, not a warranty
For a simplified linear instrument, price distance multiplied by quantity and contract value gives a pre-cost loss estimate at the stop price. Currency conversion, commissions and instrument-specific mechanics may add terms. Slippage or a market gap can make the realised result differ from that estimate.
Use the sizing article to keep lots, contracts, money allocation and stop-based risk separate. A monetary order amount does not automatically mean a maximum monetary loss, particularly on derivatives. Leverage changes financing and margin requirements rather than erasing economic exposure.
Plan the abnormal day
Write down what you will inspect after a connection interruption, an ambiguous management message or a rejected protective order. Determine which accepted orders reside at the destination and which future actions need the copier to remain online. A manual response should start by reconciling the existing state, not by assuming the failed screen means nothing happened.
| Event | Account question |
|---|---|
| Several entries arrive together | What is total open exposure? |
| One protective instruction fails | Which position remains unprotected? |
| Connection resumes | Are old orders already present? |
| Source changes its format | Does interpretation still match intent? |
| Route is disabled | What happens to existing positions? |
Keep evidence that can change a decision
Track rejected instructions, unexpected quantities and management mismatches as well as completed trades. A useful review includes costs and losing periods, not just a gallery of successful targets. Decide beforehand which observed failures require pausing the route and investigating.
Test configuration changes on demo before returning the route to live use. For evaluation accounts, separately check the firm's current terms in the prop-firm article; a technically functioning copier does not establish permission to use a particular signal source.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay