How checks work

What a platform check verifies—and what it doesn’t

CodeFlowOS can send supported MQL5 and cTrader C# output through a platform compile workflow. A completed “passed” result means that workflow reported the submitted code compiled successfully under its configured environment.

What a passed check tells you

• The compiler workflow processed the code snapshot submitted for that check and reported no compile errors.
• A failed check can return compiler diagnostics to help locate syntax or type errors in the submitted code.
• The result applies only to the submitted snapshot and configured compiler environment. If you edit the file afterward, check the edited version again.

What it does not prove

• It does not prove that the translation preserves the source strategy’s signals, timing, position sizing, or exits.
• It does not compare Pine Script and MQL5 backtest results. Pine Script does not have a compiler check in this pipeline.
• It does not establish profitability, eliminate trading risk, or guarantee that a broker will accept or fill an order.
• It does not replace reviewing warnings, runtime behavior, symbol settings, broker rules, or risk controls in the target platform.

How to check behavioral parity

1. Match the symbol, timeframe, date range, source prices, indicator inputs, strategy settings, and position-sizing rules.
2. Compare timestamped signal direction on the same completed bars before comparing orders, profit, or drawdown.
3. Review fill timing, spread, commission, slippage, data history, account mode, and order outcomes separately.
4. Test the exact converted file in the target platform and use out-of-sample and demo workflows before considering live use.

Read the guide to comparing Pine Script and MQL5 behavior or follow the conversion walkthrough. The converter and its optional checks are available on the CodeFlowOS home page.