Skip to main content
This screen is part of the Vole Bot package.
An instance is one running copy of a strategy — a strategy paired with a broker, a symbol, and a timeframe. Instances is where you see every instance you’ve created and where you create new ones.

The table

Each row shows the symbol, the strategy it runs, its timeframe, its execution mode (see below), its position size (with leverage shown beneath it), its exit method, and its realized performance so far: trade count, win rate, net P&L in dollars and percent, and profit factor. Hovering a column header explains exactly what it’s measuring. An “only active” filter hides paused instances so the table stays focused on what’s actually trading. Each row has an Edit button and a Pause / Activate button that turns the instance off or on. Use the Broker filter at the top right to show a single broker; each row then also gets a Delete button.

Execution mode

Every Binance instance runs in one of three modes:
  • Simulation — offline, no calls to the broker at all.
  • Demo — the broker’s real matching engine, with fake money.
  • Live — real money, real orders.
Interactive Brokers instances have no mode of their own: their form has no Execution Mode box and their rows show no mode. Whether Interactive Brokers trades on its paper account or with real money is one setting for the whole broker, on the Interactive Brokers card in Bot Settings, and every Interactive Brokers instance follows it.

Creating an instance

New Instance opens a form:
  • Strategy and Version (defaults to whichever version is ACTIVE — see Versions).
  • Symbol and Timeframe.
  • Execution Mode (Binance only — see above).
  • An Execution Policy picker — leave it on Legacy mode to set exit rules by hand on this form, or attach a saved policy so this instance follows the same rules as any other instance using it. Picking a policy fills in the exit settings below and locks them. To change one for this instance alone, tick Manual override (advanced); the instance then stops following the policy. See Execution Policies.
  • Exit Method — Standard or Pro Exit. Standard gives you a Bracket Order: a take-profit and a stop-loss, each set as a percentage distance from your entry price. Pro Exit has no bracket order; it replaces it with its own Stop Loss and take-profit settings and the Pro Exit Modules list. See Exit Rules.
  • Reverse Signal Behavior (Pro Exit only) — what the bot does when your strategy signals the opposite direction while this instance holds a position. Close and flip closes the position and opens the other side; Keep the position holds it and ignores the signal. Standard has no such choice and always closes and flips. While an Execution Policy is attached, this choice is read-only and shows the one that applies, marked Policy when it comes from the policy; tick Manual override (advanced) to set it for this instance alone. See Exit Rules.
  • Optional Notes.
Before you save, Preview replays the real bot logic for this exact configuration over a choice of recent windows, in either a fast bar-close mode or a slower, more faithful minute-by-minute mode. It’s an approximate look at how this setup would have behaved — not a substitute for a full backtest, but a quick sanity check before you commit to it.

Stopping or removing an instance

To stop an instance, press its Pause button. The same button turns it back on with Activate. If the instance has no open position, it stops straight away. If it holds an open position, a Stop instance — open position dialog opens first. It names the position (side, size, symbol, entry price and when it opened) and tells you what stopping will do: the bot that owns the position closes it at the market price, and only then does the instance stop. You choose:
  • Close position, then stop — the bot closes the position on its next cycle and then switches the instance off. Until it has, the instance stays active. If the bot isn’t running at that moment, the close happens when it starts again.
  • Keep running — cancels, and nothing changes.
If the broker can’t confirm that the position is really open, the bot closes nothing, the instance stays active, and you are told on Telegram. If you have already asked for a close and it hasn’t happened yet, the dialog says Close already requested and offers only OK. Deleting works differently. For an instance with no open position, the Delete instance dialog asks you to confirm with Delete or Cancel; its trade history stays, but the instance itself can’t be recovered. An instance with an open position can’t be deleted at all. A Cannot delete — open position dialog tells you to stop it first, which closes the position, and then delete it.