Skip to content
Guides
FROpen Studio

Export and manage

Resolve a problem

Useful checks before resuming work or contacting support.

3 min read · 8 sections
Contents of this guide

Studio does not display correctly

Record the exact message and affected screen. If Retry is available, use it once and observe the result. If the issue persists, reload and check that you are signed in to the intended account.

Avoid immediately clearing browser data: local information may help investigate the issue. Include the page address, browser, time and a focused screenshot when contacting support.

Copilot does not finish a reply

A missing or interrupted answer does not automatically mean the strategy is invalid. Inspect request status and the displayed message. Check your balance if a credit limit is reported.

For a modification request, review the saved rules before repeating it. Use the offered recovery actions and include the request identifier when reporting the issue. A service may remain temporarily unavailable despite recovery options; absence of every incident cannot be promised.

A requested setting is missing

Check the selected strategy and version. Read the reply to distinguish a proposal from an applied modification. Then inspect Flow or strategy controls and look for a save action.

For cTrader, compare the exported file and its exposed parameters. A value in a conversation or a code constant is not automatically an adjustable interface setting.

A backtest produces no trades

CheckWhat to look for
Operation statusCompleted, running or failed
Data and datesCoverage of the intended market and period
ConditionsCompatible combination, direction and thresholds
SessionsA window that actually permits entries
Initial historyEnough context for the chosen conditions
Protections and sizeValid values and units for the test

Simplify a working copy to isolate a condition, then compare. Preserve the baseline. No trades cannot measure performance where the strategy had no entry opportunity.

Two reports disagree

First compare version, dataset, dates, capital and costs. Then check the displayed scope: closed outcomes, open positions, a subgroup or the full period.

Do not adjust rules merely to force two numbers to match. Identify a concrete difference and examine an operation or period where the reports diverge.

A metric displays a dash

A dash can indicate missing information or a measure that cannot be calculated in the current case. A gains-to-losses ratio with no losing trade is one example requiring careful interpretation.

Check the definition and sample. Do not treat an absent value as zero or replace it with an unlabelled estimate.

Export or compilation fails

Check that rules are saved and the selected format matches your purpose. Record the exact message. For manually edited code, identify the last change and retain a copy before correcting it.

Successful compilation still needs rule review and demonstration observations. See Code and Export.

Prepare a useful issue report

Text
Screen and page address:
Action performed:
Expected result:
Observed result and exact message:
Strategy/version and period when relevant:
Time and request identifier when displayed:
Screenshot limited to the relevant area:

>

Search the guides