1) Earlier than you publish a remark
- Attempt to reproduce the problem and word the precise time (terminal time).
- Double-check the product settings (inputs), image, and mode (market/pending).
- Be sure you are utilizing the most recent product model and terminal construct.
2) What you will need to embody in your remark message
- Image (e.g., EURUSD) and occasion time (date + precise time in terminal).
- Motion sort: BUY/SELL, Market/Pending, lot measurement.
- Anticipated vs Precise: what you anticipated and what truly occurred.
- Connect the set file (inputs) if the product makes use of parameters.
Tip: you could blur your account quantity on screenshots. However logs must be hooked up in full at any time when potential.
3) Level to ONE particular commerce (or sign), not “general”
To find the occasion rapidly within the logs, reference one thing concrete:
- Ticket quantity from Historical past, or
- precise time + image + entry worth, or
- for copiers/indicators — the sign textual content precisely as acquired + what the terminal did.
4) What logs are wanted (in 99% of circumstances)
Consultants (professional/advisor/utility log)
Journal (terminal journal)
Vital: “Consultants” shows product messages, whereas “Journal” shows terminal system occasions and buying and selling server responses. Sometimes, each are wanted for diagnostics.
5) The best way to save logs to a file
Possibility A (straightforward): open the info folder and take the recordsdata you want
- Within the terminal, open the menu: File → Open Knowledge Folder .
- The additional path will depend on the platform:
- MT4 :
- Consultants logs: MQL4Logs
- Terminal logs (Journal): Logs
- MT5 :
- Consultants logs: MQL5Logs
- Terminal logs (Journal): Logs
Log recordsdata are usually date-based. Connect the logs from the identical day the problem occurred (and the adjoining day if it occurred round midnight). Ideally, zip them into one .zip: one file from Consultants + one file from Journal.
+ Please point out within the remark which particular commerce had the issue in order that we will discover and consider the info on it within the logs.
Possibility B: Copy textual content from Consultants/Journal tabs
- Open the Consultants or Journal tab.
- Proper-click on the messages listing.
- Use Copy and paste into your message (or save to file in case your terminal menu offers it).
Possibility A is most popular as a result of the uncooked log recordsdata are extra full and time-accurate.
6) Should you see an order opening error — it’s not random
When an EA/utility studies a gap error, there’s virtually at all times a particular cause: unsuitable order sort, invalid worth, SL/TP too shut, dealer restrictions, excessive unfold, cease degree, market closed, and so forth. That’s why the precise commerce parameters are crucial:
- Entry worth the product tried
- Precise SL and TP values
- Order sort (Market/Pending; Purchase/Promote)
- Time of the try
- The precise error message from the log
7) For commerce copiers / sign instruments: connect the sign instance
- Sign textual content precisely as acquired (Telegram/Discord/e-mail/file, and so forth.).
- Log/screenshot displaying how the product parsed the sign and what it tried to open.
- End in Historical past/chart: what was truly opened (or not opened).
8) The best way to write in feedback: brief and factual
The remark part will not be a chat. The clearer and extra structured your report is, the sooner you get a significant response.
Dangerous: “Nothing works. Repair it.”
Good: “MT5, EURUSD, 2026-01-24 14:37 terminal time. Sign: BUY 1.08500 SL 1.08350 TP 1.08800. Anticipated market entry; Consultants reveals error X. Connected Journal + Consultants + set.”
9) What’s prohibited (will probably be thought of spam)
- Promoting indicators, channels, third-party providers, or promotional hyperlinks.
- Selling different merchandise like “one other copier works completely”.
- Spamming feedback with out details (logs/examples) and with no particular case.
Such messages could also be eliminated. Repeated violations could end in a ban.
10) Help request template (copy & fill)
Image: ___ Date/time (terminal time): ___ Challenge abstract (Anticipated vs Precise): – Anticipated: ___ – Precise: ___ Commerce particulars: – Ticket/time: ___ – Kind: BUY/SELL Market/Pending – Entry: ___ – SL: ___ – TP: ___ – Lot: ___ Attachments: – Consultants log: hooked up (file/zip) – Journal log: hooked up (file/zip) – set file: hooked up (if relevant) – sign instance: hooked up (if relevant)
Present structured details — and also you’ll get a structured, actionable reply.
