StratBase.aiStratBase.ai
DashboardCreate BacktestMy BacktestsCatalogBlogNewsToolsHelp

Products

  • Researcher Dashboard
  • Create Backtest
  • My Backtests
  • Catalog
  • Blog
  • News

Alerts

  • Calendar
  • OI Screener
  • Funding Rate
  • REKT
  • Pump/Dump

Company

  • About Us
  • Pricing
  • Affiliate
  • AI Widget
  • Contact

Legal

  • Privacy
  • Terms
  • Refund Policy

Support

  • Help Center
  • Reviews
StratBase.aiStratBase.ai

Think it. Test it.

StratBase.ai does not provide financial advice or trading recommendations. AI only formalizes user ideas into testable strategy configurations for research purposes. Past backtesting performance does not guarantee future results. All trading decisions and associated risks are the sole responsibility of the user. This platform is not a broker and does not facilitate real trading.

© 2026 StratBase.ai · AI-powered strategy research and backtesting platform

support@stratbase.ai
Help Center/Troubleshooting/Backtest Won't Start or Fails

Backtest Won't Start or Fails

🔧Troubleshooting
📌

Backtest Won't Start or Fails

If your backtest won't start, gets stuck, or fails with an error, use this troubleshooting guide.

📌

Backtest Status Flow

A backtest moves through these statuses:

draft → queued → running → completed
                         → failed
                         → cancelled
🔧

Common Issues

"Queued" for a Long Time

Cause: The Celery worker may be busy processing other backtests.

Solutions:

  • Wait a few minutes — backtests are processed in order
  • If stuck for more than 10 minutes, try cancelling and resubmitting
  • Check your internet connection and refresh the page

"Failed" Status

Common causes:

| Cause | Solution | |-------|----------| | No data available | Check data coverage for your instrument + timeframe + period | | Invalid strategy | Ensure at least one entry condition is set | | Timeframe mismatch | Some instruments don't support all timeframes | | Period too long | Free plan: max 1 year. Check your plan's limits | | Server error | Try again in a few minutes |

"Running" but No Progress

Cause: The progress WebSocket may have disconnected.

Solutions:

  • Refresh the page — the backtest continues on the server
  • Check the progress bar — it updates via WebSocket
  • Wait for completion — you'll receive a notification

No Trades Found

If the backtest completes but shows 0 trades:

  1. Check entry conditions — they may be too restrictive
  2. Check the time period — may not have enough data
  3. Check the indicator parameters — extreme values can prevent signals
  4. Try a longer period or simpler conditions
📌

Data Coverage

Before running a backtest, verify data availability:

  1. Go to Backtest → New
  2. Select your instrument
  3. The system shows available data range
  4. Adjust your test period to fit within available data

Tip: Use the /data-coverage page to check all available instruments and their date ranges.

📌

Free Plan Limits

| Limit | Value | |-------|-------| | Backtests per day | 5 | | Max timeframe | 1 minute | | Max period | 1 year | | Optimization | Not available | | AI Analysis | Not available |

Upgrade to Pro or higher to remove limits.

❓

FAQ

Q: My backtest was running but now says "running" forever? A: This can happen if the server was restarted. Contact support — they can reset the status.

Q: Can I run multiple backtests simultaneously? A: Backtests are queued and processed one at a time per user.

Q: The results seem wrong — what do I check? A: Verify your commission settings, leverage, and position sizing mode. Small changes in these settings can dramatically affect results.

🔗

Related Articles

  • Your First Backtest
  • Data Coverage
  • Entry Conditions
  • Key Metrics Explained