Why does my backtest succeed but demo trading fail to start?
Last updated ·
Find the first startup or order error, then check the stage where execution failed.
Find the first error
Exchange-connected execution must read the account, load contracts, validate configuration, subscribe to market data and pass order checks. Open the instance logs and locate the earliest explicit error.
If no instance was created, check deployment preparation and account access. If an instance is running without fills, inspect signals and order records.
| Failure stage | Check |
|---|---|
| Account read failed | Credential environment, permissions, network and original response |
| Contract not found | Full symbol, market type and demo support |
| Configuration validation failed | Parameters, strategy version, Runtime version and revision |
| Order rejected | Account mode, position mode, margin, side and quantity |
| No orders submitted | Market data, signals, trading hours, warm-up and restrictions |
Verify the account and contract
Confirm that the credentials belong to the selected demo environment, the account type matches the strategy, and the account-read test passes.
Use the full contract symbol and query contract information in the target demo environment. Check production and demo availability separately.
Check saved credentials and connection results
Save the form and run the connection test. When entering credentials through remote desktop, verify that the complete Key and Secret were entered into their respective fields.
For cloud authentication failures, compare the saved values on the local and cloud machines, then check permissions, environment and IP restrictions.
Verify recovery
Confirm that account access, contract loading, market-data updates and configuration validation pass, then inspect the actual instance.
For existing orders, check their final accepted, filled, canceled or rejected status. To act on a missed signal, check whether the strategy supports catch-up orders and how long the signal remains valid.