Backtest Progress And Statuses
Backtests move through queue, execution, and result states. The table status tells you the overall state, while progress stage and percent show where a running job is inside the worker pipeline.
What this is
This article explains the statuses and progress stages shown by current backtest flows.
Statuses
pending
The run record exists and the command has been queued. A short pending period is normal.
running
The worker accepted the job and is processing market data, strategy logic, metrics, or saving.
completed
The run finished and result data is available.
failed
The run did not produce a valid result. The row or detail page can include an error message.
Progress stages
Current worker stages can include:
- syncing
- loading_candles
- validating_candles
- preparing_data
- running
- computing_metrics
- saving
All-coins runs use a similar pipeline but can spend more time in preparation and candle loading.
What to do
- For pending , wait briefly and refresh later if needed.
- For running , watch progress and avoid submitting duplicate runs unless you intended to compare variants.
- For completed , open the result page.
- For failed , read the error, then check dates, symbol, exchange, and data availability.
Common mistakes
- treating pending as failed too early
- assuming progress must move linearly every second
- ignoring a failed row's error message
- comparing a completed historical result with live Analytics without checking the time period
Related articles
- Run Backtest
- How To Read Backtest Report
- Plans And Limits