EA installed but not running: a practical troubleshooting order
Check the terminal, file version, chart and permissions, then inspect the log. Prepare a reproducible issue rather than a profit screenshot.
Niubang editorial · Updated
01 Identify the exact terminal
With several terminals installed, a file can end up in one instance while another is open. Record the terminal version, data directory, EA filename and version. Installation support requires files you are authorized to use; it cannot replace missing licensing rights.
02 Separate loading from execution
In MT5, check the EA name and status icon on the chart. Trade permission involves both application and platform settings. A chart runs one EA at a time. Loading an EA does not prove that its trading conditions are currently met.
03 Prepare a reproducible issue
Record the environment, version, inputs, action, expected result and observed result. Keep the relevant timestamped log and redact secrets. A demo-terminal error with steps to reproduce is more useful for troubleshooting than a return screenshot.
04 Review the handover
Agree on the number of EAs and terminals, VPS involvement and any dependency on the original developer. List third-party charges separately. Expect a version record, work performed, checks and remaining limits. Submit these materials for a scoped installation consultation; technical completion does not establish profitability.