Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA missing MT5 entry is an observation to investigate, not proof that an Expert Advisor (EA) received a valid signal. Trace the event through four checkpoints: whether the relevant price history covers the symbol and time, whether the EA evaluated its entry condition, whether it sent a trade request and what happened to it, and whether an order or deal appears in history. Missing bars or ticks make the evidence incomplete; they do not establish that an entry rule became true.
Freeze the event context before investigating
Write down the details needed to reproduce the same event. A live chart and a Strategy Tester run are different contexts, and repeated tests may not describe the same event if their settings or EA version differ.
As an Amazon Associate I earn from qualifying purchases.
- Symbol and timeframe.
- Event time, including the broker-server timestamp and timezone used to identify it.
- EA name and build, plus its input values.
- Whether the claim comes from a live chart or the Strategy Tester. For a test, record the date range and modelling mode.
- The exact tester settings and, if available, the relevant EA binary or source code.
Keep the time basis explicit: MetaTrader’s platform Journal uses local-computer time, while the event may be described in broker-server time. Align the timestamps before deciding that two log entries refer to the same event. See MetaQuotes’ Platform Logs.
Check whether the relevant price history was available
For a tester run, inspect the Strategy Tester journal for history download or synchronization messages, tick-data checks, the earliest available history time, and any indication that the test start was shifted. MetaTrader documents that the tester synchronizes price history and may download missing data. It also needs preceding bars for indicator calculations; if the available history cannot supply the required bars, the actual test start can move forward. The tester’s history requirements are documented in How the Tester Downloads Historical Data and the Strategy Testing help page.
#1 Best Overall
The help page states: “The tester requires at least 100 bars on the selected timeframe before modeling can begin.” This is a condition for tester initialization on the selected timeframe, not a universal requirement for every live EA.
Do not treat bars and ticks as interchangeable
Minute bars and ticks describe price history differently. The MQL5 testing reference describes cases in which the tester generates ticks when minute bars exist without ticks, as well as cases where tick history does not align with minute bars. A gap or mismatch is therefore a data-coverage or data-quality uncertainty to investigate against the expected trading session and available broker history—not evidence that a strategy signal occurred or failed. See Testing Trading Strategies and MetaQuotes’ Journal of Testing.
Find out whether the EA evaluated its entry condition
Once you have checked history coverage, inspect the EA and terminal records around the event time. The Experts log contains messages from EAs and indicators; the platform Journal records terminal events, including trade operations. Read both rather than relying on a chart or a single log. Their roles are described in MetaQuotes’ Platform Logs.
A log message may show that the EA ran, but that alone does not prove its entry condition evaluated as true. To establish that checkpoint, look for EA output that identifies the condition or decision, or inspect the EA’s logic and reproduce the event with matching inputs and history. Without that evidence, distinguish “the EA was active” from “the entry rule was satisfied.”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check for a trade request, then an order or deal
In the Strategy Tester, use Toolbox history to inspect orders and deals, and check the history of EA trade requests. The tester’s trade-history views are described in MetaQuotes’ Strategy Testing help.
- A request is present, but no resulting deal appears: inspect the request outcome and tester or broker response before calling it a missed signal. A request and an executed deal are separate checkpoints.
- A deal appears: investigate whether the apparent miss comes from the chart, the EA’s state, or how the event is being reported.
- No request appears: check whether the EA evaluated the entry condition and whether the relevant history was available. The absence of a request by itself does not tell you which checkpoint failed.
These branches are ways to interpret the records, not a diagnosis of any particular account or EA. Use the available logs and history to locate where the evidence stops.
Keep data uncertainty separate from strategy logic
Use the four checkpoints to state what is established and what remains unknown:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Price history: Was the relevant symbol and interval covered by the bars or ticks used for the live event or test?
- EA evaluation: Is there evidence the EA evaluated its entry condition, and what decision did it record?
- Trade request: Did the EA send a request, and what response or outcome is recorded?
- Order or deal: Does trade history show an order or executed deal?
If the event time, EA logic and build, settings, logs, or market-history coverage are unavailable, the cause cannot be assigned confidently. Describe the missing checkpoint rather than inferring that an entry signal existed from missing data.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
