> ## Documentation Index
> Fetch the complete documentation index at: https://help.vole.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Debug

> [!NOTE]
>
> This screen is part of the Vole Bot package.

Debug steps through a strategy bar by bar to answer one question: why did it
fire the signals it fired — or why did it fire so few, or none at all. It's
the tool to reach for when a backtest looks empty or strange and you need to
see the mechanics behind it, not just the summary.

## Setting it up

Pick a **Strategy**, a **Symbol**, a **Timeframe**, and how many days of
history to analyze, plus a take-profit and stop-loss percentage used for the
simulated trades in this analysis. Then **Run Analysis**.

## Reading the result

The top of the results names exactly what was analyzed — which version, and
whether it used the parameters you set on this screen or the ones already
saved with the strategy — so you're never unsure what the numbers below
belong to.

* **Chart** — the price candles for the window you chose, with the
  strategy's signals marked on them, so you can see a signal in context
  rather than as a row in a table.
* **Signal metrics** — how many bars were analyzed in total, how many came
  out long, short, or flat, how often the direction flipped, the longest
  stretch with no signal at all, and where the first signal appeared.
* **Condition counts** — how many bars satisfied the strategy's long and
  short entry condition on their own, and how many of those were held back
  because the bot was already in a position on that side — the difference
  between "the condition fired" and "a new entry actually happened."
* **Trade metrics** — how many simulated trades resulted, their net profit,
  win rate, and profit factor, plus how many were closed by timing out
  rather than by a signal or the stop/target.
* **Events** — a bar-by-bar log of every open and close: when it happened,
  which side, why, at what price, its profit or loss, and the take-profit /
  stop-loss levels in force at the time.
* **Diagnosis** — a short, plain-language note on anything that looks off
  (for example, signals that are too sparse or too one-sided), or a
  confirmation that nothing unusual turned up.

You may see this screen referred to elsewhere as "Signal Debug" — same page,
listed here as "Debug" to match the menu.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.