Why Backtest Is Required Before Launch

Backtesting is not optional preparation. It is the first launch gate. A bot that has never passed a backtest cannot be started.

What this is

This article explains why the platform requires a saved bot to complete a valid backtest before its first start command is allowed. If an already validated bot changes configuration later, the platform shows a stale-backtest warning instead of requiring a new run to start.

When to use it

Use this article if:

- the platform tells you to run a backtest before starting a bot

- you want to understand what the launch gate checks

- you need to know why a bot still cannot start after configuration is complete

Before you start

Important behavior:

- the bot must be saved before the normal bot-centered backtest flow can run

- a successful backtest is required before a never-validated bot can start

- email verification is also required for running backtests and bots

- allowed backtest periods depend on the subscription plan

- Free-plan backtests are forced public in the saved-bot flow

Step by step

Step 1: Save the bot first

If the bot only exists as unsaved editor state, the normal run-for-bot flow is not ready yet. Save the bot so the platform has a stable configuration record to test and later launch.

Step 2: Run the backtest from the editor or dashboard

You can run the saved-bot backtest flow from:

- the editor, for an existing saved bot

- the main dashboard, through Run Backtest

In this flow, the standard initial balance is currently 1000 .

Step 3: Choose a period your plan actually allows

Plan limits matter here:

- Free allows 1 and 3 month periods

- Basic and Pro allow 1 , 3 , 6 , and 12 month periods

If you choose a period outside your plan allowance, the run is blocked.

Step 4: Read the warnings, not only the final PnL

Backtests can include warnings when some parts of the live strategy do not replay perfectly in historical mode.

Examples include:

- TradingView signal rules ignored during historical replay

- funding-rate data unavailable

- open-interest data unavailable

- all-coins universe handled with additional caveats

Step 5: Understand how config changes affect the last backtest

If you edit a bot in a way that affects its strategy after it already passed the launch gate, the previous backtest remains saved but is marked as stale.

That warning means the current config no longer matches the old backtest. It does not block start by itself, but you should run a fresh backtest before relying on the analytics again.

Step 6: Start only after the gate clears

Once the backtest completes successfully and the bot is marked as passed, return to the dashboard and use Start .

If Start still fails after that, the next likely checks are:

- email verification

- available balance above zero

- runtime or account-specific issues unrelated to the config

What you should see

After a successful backtest flow, you should have:

- a completed backtest record

- a report you can review

- the required-backtest gate cleared, or the stale-backtest warning cleared after a matching retest

- permission to start the bot if the other launch checks also pass

Common mistakes

- trying to start a bot that was configured but never saved

- assuming a pending or failed backtest is enough to unlock launch

- ignoring plan-based period restrictions

- running a backtest with warnings and treating it as a perfect live proxy

- forgetting that the platform still checks available balance at launch

- Run Backtest

- How To Read Backtest Report

- Save, Edit, Clone, And Launch

- Bot Statuses And Status Reason