Deployment & Simulation Troubleshooting Flowchart

Failure Path 1

Data Integrity Exception

Root Cause

The historical data provided is incomplete or malformed—for example, fewer than 50 candles, or OHLCV data points contain zero values.

Why It Happens

BitThor requires a minimum volume of clean, complete data to reliably calculate indicator signals and simulate trades. If the data source is too sparse or contains gaps, the analysis engine cannot produce meaningful results.

Remediation

1. Check Data Source: Ensure your selected symbol has historical data available for at least the last 50 candles.
2. Verify Data Quality: Confirm the data source contains non-zero values for Open, High, Low, Close, and Volume for all required candles.
3. Select Alternative Symbol: Choose a different, well-supported symbol, or wait for more historical data to be populated.

Failure Path 2

Configuration Hash Mismatch

Root Cause

The current settings used to run the simulation do not exactly match the configuration saved when the simulation was originally run—for example, you changed an indicator period or advanced parameter.

Why It Happens

This is a critical safety feature. BitThor will not deploy a bot with a configuration that differs from the audited simulation snapshot, as it could lead to unexpected performance.

4-Step Recovery

1. Identify Change: Note exactly which setting (Indicator, Factor, etc.) was changed after the simulation was recorded.
2. Update & Re-Save: Apply the intended change in the Bot Editor and save a new Blueprint Draft.
3. Re-Simulate: Run a new simulation using the updated, saved Blueprint Draft.
4. Re-Deploy: Use the new simulation session ID for the final deployment confirmation.

Failure Path 3

Connection Error or Invalid Token

Root Cause

The live connection to the exchange, or the temporary activation token, has expired or is unavailable.

Why It Happens

The deployment process requires the live market analyzer to be actively connected and authenticated. Tokens have a finite lifespan and network conditions can interrupt exchange connectivity.

Remediation

1. Check Connectivity: Verify your internet connection is stable and the exchange is reachable.
2. Wait & Retry: If the error is connection-related, wait a few minutes and attempt the “Retry Verification” step.
3. Check Credentials: If the error persists, verify your API keys and secret within the BitThor Settings panel.

Failure Path 4

Missing Market Regime Context

Root Cause

A simulation run submitted via the API did not include the required marketRegime field, or the value provided did not match one of the accepted regime labels.

Why It Happens

BitThor captures the market regime at the time of simulation to support audit traceability across different market conditions. Non-wizard API calls must supply this field explicitly; the Setup Wizard supplies it automatically using a Sideways default when no value is provided.

Accepted Values

Bullish, Bearish, Sideways, Volatile — case-insensitive. Any other string is rejected with a 400 status.

Remediation

1. Add the field: Include "marketRegime": "Sideways" (or the appropriate regime label) in your simulation request body.
2. Verify the value: Confirm the value is one of the four accepted labels and contains no extra whitespace or special characters.
3. Re-submit: Retry the simulation request with the corrected payload.