Free source-safe diagnosis guide
A controlled evidence checklist for custom cTrader indicators that stop building, loading or plotting after a desktop or Algo API update.
Confirm whether the failing item is a built-in indicator or a custom C# or Python project. Custom indicators run only in supported desktop applications, not cTrader Web or Mobile.
Back up the editable project and exact installed .algo package before changing it. Protected Store code is not decompiled or reconstructed from a compiled file.
Record the last known working cTrader version, operating system, indicator version, symbol, timeframe and parameters.
Record the current cTrader and Algo API versions, application type, account and workspace context, plus whether cloud synchronization is enabled.
Copy the complete build-result errors and warnings. The first compiler diagnostic is usually more useful than a screenshot showing only an empty chart.
Attach one rebuilt indicator to one liquid symbol and timeframe with defaults. Do not mix templates, multiple copies and parameter experiments into the first reproduction.
List custom indicator references, NuGet packages, files, internet calls and access rights. Verify each dependency against the current runtime separately.
Log initialization and calculation checkpoints and inspect output values. An instance can load correctly while returning NaN, drawing off-scale or writing to an unexpected panel.
Create or retain a smallest authorized-source case that exercises the suspected API member without the trading logic. This isolates platform compatibility from strategy behavior.
Require a clean rebuild and one before/after chart case on the captured environment. Treat broader redesign, new features and trading logic as separate scope.
No. First separate application support, installation state, build diagnostics, dependencies and output behavior. A platform update is a time correlation, not a proven source-code cause.
Not by modifying protected code. The seller or cTrader support should handle the original product. A clean reimplementation requires explicit behavioral requirements and authorization, and is a separate project.
No. Use authorized source, build output, redacted configuration and a demo or no-transaction reproduction. Credentials and autonomous live-account operation are outside scope.
Free diagnostic resource
Mark Build, Load, Calculate and Plot in order, then copy a source-safe evidence brief without uploading code or credentials.
Open the free toolReady for a feasibility check?