Automation and risk: what the rules do not remove

01

Automation moves decisions; it does not erase them

An automated workflow applies rules you selected to supported messages. That can reduce repeated manual steps, but it cannot make the source accurate, know whether a strategy still suits you, or protect an account from every market move. Parsing a message correctly and deciding that it should become a trade are two different judgments.

Treat the profile as an instruction set that deserves review, not as a substitute for oversight. You choose the source, account, exposure settings, and circumstances in which automation should be paused. If you cannot explain what a rule means or which orders it can affect, do not enable it simply because the form accepts a value.

02

Per-order sizing is not a daily loss cap

Current profile controls include fixed lot or a risk percentage of balance, plus limits such as maximum lot, order count, cooldown, and distance checks. These controls apply to decisions about an order; they do not establish one universal ceiling on all account losses. In particular, a per-order risk setting should not be read as a daily profit or daily loss limit.

A percentage is only as useful as its assumptions. Confirm which balance figure is used, how the instrument's tick value and broker contract details affect the calculation, and what happens if a stop is missing or too close. Market movement, gaps, margin rules, and execution prices can make realized loss differ from a planned amount.

Daily profit and loss limits are a separate question from the risk on one order. Review any daily-stop settings independently: what they measure, which accounts they affect and whether they pause new entries or act on existing positions. A small lot size alone is not a daily loss limit. Make sure the behavior you choose matches your overall risk plan.

03

Multiple entries change total exposure

TTMT supports multiple-order and signal-based second-entry behavior in the current profile path. A reply that uses LAYER has defined ownership semantics; it is not a promise of an automatic grid, martingale, or redistribution of risk across every target. Each entry still needs its own sizing and broker checks, and several individually small orders can add up to meaningful exposure.

For any layered or multi-target approach, check whether the configured risk applies to each order or to the combined position. Entry weighting and target distribution can change that relationship. Do not assume one intended risk budget is automatically shared across all entries; review the selected settings and test the complete example with a demo account.

04

Stops and price filters cannot guarantee a fill

A stop loss is an instruction that depends on broker behavior and market conditions; it is not a fixed guarantee of the final exit price. Gaps, fast markets, liquidity, and broker rules can change the fill or prevent an order from being accepted. A maximum-slippage or favorable-price filter can reject some entries, but it cannot promise zero slippage for every order.

Check the relationship between signal prices and the broker's quote before relying on an entry. Trading-hour filters use the broker server's time, which can differ from your local clock. A symbol mapping should be verified against the actual account catalog, and passing a text check does not prove that the broker permits a particular volume or stop distance.

05

Pausing is not the same as closing

Pausing execution can stop eligible future instructions from proceeding, but it does not automatically close positions that are already open or cancel every pending order. Closing a position is a separate account action with its own target, permissions, and broker response. Know exactly which positions and pending orders remain after you pause a source or account route.

Before using a close or break-even action, check exactly which positions it targets. An account-level action and a channel-level action need not affect the same trades. Read the confirmation, make sure the account is connected, and inspect the result rather than assuming that pressing the control means every position has changed.

06

Watch the evidence, not only the sent instruction

A useful audit trail distinguishes a signal received, a profile decision, a command sent, and a broker-confirmed effect. An accepted or queued command is not the same as a confirmed trade. When a result is uncertain or reconciling, wait for broker evidence and check the activity history before considering another attempt.

Position and performance views can include data freshness and completeness cues. A delayed or stale snapshot is a reason to verify the broker account directly before making a consequential decision. Historical analytics summarize available broker records; they do not establish a future result, explain every external position, or make past performance predictive.

07

Keep a monitoring and contingency plan

Decide how often you will check the account, which status signals require action, and how you can reach the broker if the platform is unavailable. Keep account access private and review who has permission to change profiles or control execution. Do not rely on a web page being open—or on an unattended cloud service—as proof that every component is currently connected.

Trading can result in losses, including losses larger than expected from an initial plan. TTMT does not provide investment advice, select a source for you, or guarantee a return or an execution outcome. Use a demo environment to understand the workflow, and make any decision about real-money trading independently and with an understanding of the risks.