Troubleshooting and Support

First identify where the problem occurs: preparing a request, generation, saving, compilation or execution. The next step depends on that distinction. Keep source and messages before clearing a task or retrying, especially when generation succeeded but saving did not.

A useful report explains the selected task, supplied material, actual result and expectation. Include the model and relevant message. For code behaviour, provide a reproducible chart or tester example rather than only a description of poor performance.

Source or attachment rejected

Check the task matches the source. Existing tasks require MQL5; MQL4 belongs in conversion. Conversion accepts one complete file up to 32 KB and requires permission confirmation. A compiled .ex5 is not editable source. Add the current codebase before trying another source role.

Images require PNG, JPEG or WebP up to 3 MB, an indicator task and a supported model. Report analysis expects a MetaTrader Strategy Tester .xlsx workbook up to 2 MB. Changing an extension does not convert contents; export again from the original application when necessary.

Errors or unexpected behaviour

For compiler problems, supply complete current .mq5 source and exact MetaEditor diagnostics to the repair task. Compile locally when automatic checking is unavailable. Identify missing includes or custom indicators before changing otherwise valid code.

For a program that compiles but behaves incorrectly, use the matching Existing task. Give symbol, timeframe, inputs, event time and journal output with the expected action. One missed entry, repeated alert or wrong volume is easier to investigate than a broad request to improve everything.

Saving, accounts and support

Sign in again if the session expires. Download source when a save error appears; a visible answer does not prove the project was saved. Check Account for transactions when credit or a payment is unclear, and avoid repeating a purchase before checking its status.

Use Report a problem for workspace issues or suggestions. Review its option to include the listed diagnostic context before sending. Supply necessary source separately where appropriate and exclude passwords, keys and card details. ClickAlgo support can also help; retain local source and evidence during investigation.