An automated trading application receives information through several event handlers, but those handlers do not necessarily observe the account at identical moments. A price update may prompt a trading decision while the server is still processing an earlier request. Meanwhile, transaction notifications can describe individual stages of execution rather than a completed position.
In mt5, OnTick, OnTrade and OnTradeTransaction serve different purposes within this process. Understanding their interaction is essential when an Expert Advisor manages CFDs through rapidly changing execution conditions. Five technical risks arise when programs confuse event notifications with confirmed account states.
Price Events Can Generate Decisions Against Outdated Position Information
OnTick responds to incoming market quotations, making it a natural location for entry signals. Yet a trade request initiated during one price event may remain unresolved when subsequent strategy logic evaluates the account.
If the program checks only current positions, it might interpret an outstanding order as an absence of exposure. Another entry can then become eligible before the first request has finished processing.
A more reliable design records pending trading intentions separately from confirmed holdings. Examine active orders, outstanding requests and actual positions together before allowing another CFD entry.
Transaction Notifications Do Not Follow a Guaranteed Business Sequence
One trading request can generate several server-side transactions, including order creation, execution, order removal and history updates. OnTradeTransaction reports these developments individually, but their arrival order should not be assumed to match a simple chronological workflow.
A program that expects an order-addition notification before every execution notification can misclassify a legitimate fill as unexpected.
Rather than depending on notification order, identify transactions through their types and relevant order or deal identifiers. Reconstruct the current account state when a notification arrives without the preceding event the strategy expected.
Partial Execution Can Produce Incorrect Hedging Calculations
Imagine a hypothetical algorithm managing a long position in a European automobile-sector index CFD. It requests 40 contracts at 520 points, with each contract worth €2 per index point. The intended notional exposure is €41,600.
The broker initially fills 15 contracts at 520, then executes the remaining 25 at 521. If the algorithm interprets the first deal notification as confirmation of all 40 contracts at 520, it records the wrong average entry and may calculate its hedge incorrectly.
The actual weighted average is 520.625 points. If the index falls to 515, the position loses €450, excluding charges: €150 on the first 15 contracts and €300 on the remaining 25. An assumed entry of 520 would instead indicate a €400 loss.
The €50 discrepancy comes from execution details, not the market signal. Accumulate confirmed deal quantities and prices before updating the strategy’s exposure calculations.
Lengthy Transaction Handlers Can Lose Important Notifications
The platform maintains a limited queue for trade transaction events. If OnTradeTransaction performs lengthy database operations or complex calculations, incoming notifications can accumulate, and older events may eventually be displaced.
More detailed logging inside the handler can therefore reduce the completeness of the record it is intended to preserve.
For mt5 applications, keep transaction processing brief and transfer heavier work to another stage of the program. Record essential identifiers immediately, monitor processing delays and reconcile against broker-maintained order and deal histories rather than relying exclusively on locally captured notifications.
General Trade Events Can Trigger Duplicate Portfolio Adjustments
OnTrade indicates that the account’s trading state has changed, but it does not provide a one-to-one correspondence with individual transaction notifications. Several OnTradeTransaction calls may be associated with a single broader trade event.
An Expert Advisor that recalculates and submits portfolio adjustments independently from both handlers risks acting twice on the same underlying change. Assign one component responsibility for generating orders, while other handlers update observations or request reconciliation.
Before opening a CFD under automated management, test partial fills and rapid successive transactions in a controlled environment, verify how pending requests are tracked, and confirm that only one handler can authorize each exposure-changing instruction.
