Simulation Troubleshooting

Troubleshooting Simulation Failures

Simulating your bot's performance is the most critical step before deploying real capital. If your simulation run encounters an error, it is usually a data requirement or a configuration mismatch — not a fatal flaw in your strategy. This guide breaks down the three most common failure codes and provides plain-language steps to get you back to simulating your edge.

INSUFFICIENT_DATA_LOOKBACK

Insufficient Data Lookback

What it means

Your bot needs enough historical data points to draw reliable conclusions. This error means the requested time period or symbol combination did not provide the minimum required candles (at least 50) for the simulation to run safely.

Root cause

The specified date range is too short, or the chosen symbol does not have historical data recorded for the required lookback window.

How to fix it

  • Switch to a supported symbol with deeper bundled history, such as BTCUSDT or ETHUSDT.
  • If you narrowed the candle window or changed the data source, widen it so the run includes at least 50 complete candles.
  • Run the data check again before starting the sample simulation.

After the longer history is available, rerun the same simulation request.

DATA_INTEGRITY_EXCEPTION

Data Integrity Exception

What it means

This error indicates that the raw data provided to the simulation engine is corrupted, incomplete, or violates fundamental data rules that BitThor requires before it can safely run.

Root cause

The historical OHLCV data contains null values, zero values in critical fields (Open, High, Low, Close, Volume), or the dataset structure is malformed. BitThor stops early to protect you from reviewing incomplete or inconsistent results.

How to fix it

  • Refresh the page and rerun the onboarding data check so BitThor can request a clean dataset.
  • If you imported or edited historical data, replace incomplete rows or switch to a bundled supported symbol.
  • If the issue repeats, restart BitThor so the simulation audit store can be rebuilt cleanly before you continue.

Try Again reuses your last simulation parameters after the data or audit issue is cleared.

HASH_MISMATCH

Configuration Hash Mismatch

What it means

This is a security and configuration validation error. It means the bot configuration the simulation used is different from the configuration currently stored in the active bot settings.

Root cause

The bot's configuration was changed after the simulation was run, or the client-side view of the bot settings is stale or outdated. BitThor stops so you do not validate one configuration and activate another by mistake.

How to fix it

  • Reload the bot or reopen the setup wizard so the latest saved settings are back in view.
  • Confirm the symbol, indicator settings, and risk controls still match what you expect.
  • Run the simulation again only after the refreshed settings are visible.

Use Try Again after the page reflects the latest saved bot configuration.

Legal Disclaimer

Resolving a simulation error only restores simulation functionality. It does not guarantee future trading success, profitability, or sustained performance. Past performance does not guarantee future results. Cryptocurrency trading involves substantial risk of loss and is not suitable for every user. BitThor provides software tools only and does not provide investment advice. Users should only trade with capital they can afford to lose and should always conduct thorough due diligence.

Return to Getting Started

Risk Disclosure: Disclaimer: BitThor is an analytical simulation and backtesting tool, not a trading signal provider or financial advisory service. BitThor provides software tools only and does not provide investment advice. All results generated are based on historical data and simulation parameters provided by the user. Past performance, including simulated results, does not guarantee future results. Cryptocurrency trading involves substantial risk of loss and is not suitable for every user. Users should only trade with capital they can afford to lose and should always conduct thorough due diligence.