Technique · Instructions
Connection, Journal & Error Messages
A systematic diagnostic sequence: first to determine the condition, then to make a targeted change.
On this page
First identify open risks and ordersDelimitation of connection and applicationOrder of trade reports by typeIf an EA does not actCreating a Helpful Diagnosis PackageReturn checked after remediationSourcesFirst identify open risks and orders
If the message is unclear, do not send the same order several times. First, check trade, pending orders and history. If no current account balance is available, use an already verified alternative access or the official broker contact. A frozen image does not show a reliably current state.
Our diagnosis sequence: Ensure observation → name possible cause → make exactly one change → re-examine the result. In this way, it remains comprehensible what actually influenced the error.
Delimitation of connection and application
- Check Internet connection outside the platform.
- MT4/MT5, account and exact server match; do not confuse demo/live.
- Differentiate investor and trade access.
- Read the login or connection message in the journal.
- If correct access is known via the official contact, clarify server malfunction, account status or change of access.
Do not disclose complete passwords for third-party support requests. A supposed remote maintenance helper may receive more rights than required for diagnosis.
Order of trade reports by type
| Observation | Possible tests; no remote diagnosis |
|---|---|
| Invalid volume | Minimum, maximum, step size and residual volume |
| Invalid stops | Direction, distance, price level and symbol conditions |
| Not enough resources | Available margin and current positions |
| Market Closed/Trade Deactivated | Trading hours, account and symbol release |
| Requote / Price changed | Execution mode, price movement and indicated deviation |
| Order not found | Time filter, incorrect account, still open pending order, missing confirmation |
The message is a starting point. It proves for itself neither manipulation nor its own operating error. Document its exact wording and the immediately preceding process.
If an EA does not act
- Is the right program started on the right chart?
- Do the symbol, time period and input parameters match its description?
- Are individual and general trade clearances set?
- Is there even the programmed entry signal?
- Do Experts/Journal reports show missing files, rights, license or connection?
An EA without an order can wait correctly for its conditions. Conversely, a visible graph is not proof of successful trading. Examine program start, signal, order request and execution separately.
Creating a Helpful Diagnosis Package
Secure journal and – in the case of automation – Experts protocol from the relevant period. The data folder of the current installation is the starting point for local files; platform and program logs can be separate. Do not randomly throw several installations together.
Editorial support scheme: time/time zone, account alias, build, icon, exact action, expected result, actual message, tickets and changes already made. crop screenshots readably and mask account numbers in the public copy. Received the original privately.
Return checked after remediation
Reconcile account status with the last secured observation. Check open positions, pending orders, stops, and active programs. If necessary, follow the same process in the demo account. No blanket new installation as a first step: It can change settings and local documents.
Sources & scope
Check the evidence.
- MT5 · Account details
Master/Investor access and server selection.
Open the source ↗ - MT5 · Orders and execution
Trade dialogue, change, closing and history; execution modes differ.
Open the source ↗ - MT5 · EA and indicators
Program launch, parameters and trading permissions.
Open the source ↗