Setup & troubleshooting
How to send a useful EA bug report without exposing your account
A useful report explains what you expected, what happened and how to reproduce it. A full desktop recording is rarely necessary and can expose account details that do not help diagnose the issue.
Include the technical identity
Record EA version, terminal build, broker symbol, timeframe and changed inputs. State whether the issue occurs in a tester or on a chart. Include the exact message and its timestamp.
Keep the evidence small
Extract the relevant Experts and Journal lines around the event. Remove login numbers, passwords, tokens and private addresses. Use a cropped screenshot only when the visible interface is relevant; do not upload complete paid source publicly.
Describe a repeatable case
Give a short sequence of steps, expected behaviour and actual behaviour. If a source modification is involved, identify it and compare with an untouched copy where practical. Keep the original package available.
Get more from the support exchange
Send the report through the support route shown on MQLume. Clear evidence helps distinguish installation questions, reproducible bugs and new feature ideas, so the next reply can address the actual issue.
Start with a free editable EA project · Explore MQLume source code
Back to top