How-to guide · Kraken API Trading Bot

How to Recover the Bot After a Kill Switch

When the kill switch fires, trading stops cold — here is the calm, checklist-driven path back to running once you understand why it triggered.

Published June 7, 2026 · Primary topic: bot kill switch recovery

← Back to the Kraken API Trading Bot hub

When the emergency kill switch fires, trading stops cold — and that is the system working, not failing. The temptation is to clear it and get back to trading as fast as possible. Resist that. Recovery is a deliberate, checklist-driven process whose first job is to understand why the switch fired, because resuming without that understanding invites the same event again.

First, do nothing fast

A kill switch fires because something crossed a line you set: a daily loss limit, a consecutive-loss streak, a drawdown threshold, or a manual stop. The line did its job. The calm response is to treat the halt as time bought, not time lost, and to work the steps in order rather than rushing back to live.

Step by step

  1. Confirm trading is halted. Verify the kill switch fully stopped new orders before you touch anything else. You want a known, frozen state to reason from.
  2. Find the trigger in the audit trail. Read the log to learn exactly what caused the switch to fire — a limit, a streak, or a manual intervention. The trail names the cause precisely.
  3. Reconcile open positions. Check which positions remain open and whether any need manual handling before you resume. A halt stops new trades; it does not necessarily close existing ones.
  4. Resolve the cause first. Address whatever tripped the switch — a limit set too tight, a strategy behaving badly, a market regime change — rather than simply clearing it and pressing on.
  5. Resume through paper if unsure. If anything is uncertain, restart in paper mode and clear the paper-to-live gate again before any live order.

Why the slow path is the safe path

A kill switch event is information. It tells you that your real conditions diverged from your assumptions enough to hit a hard limit. Recovering carefully turns that event into a fix; recovering carelessly turns it into a repeat. There is no prize for resuming a minute sooner and every reason to resume correctly.

The whole recovery runs through the execution audit trail. To understand the limits that fire the switch, the risk management pillar covers daily caps, cooldowns, and drawdown thresholds, and paper mode vs live mode explains the gate you re-clear before going live again.

Important

This is not investment advice.

GreatDane Trades is an education, backtesting, and trading automation platform. Nothing on this site is financial advice. Results are simulated. Backtests do not guarantee future results. Markets can diverge from simulations. Trading cryptocurrencies involves substantial risk including the total loss of capital. Paper trading should come before live trading. Users are responsible for their own trades.

Read the full risk disclaimer →

More in Kraken API Trading Bot

Closely related guides in this topic cluster.

See every guide in this cluster on the hub: Kraken API Trading Bot.

Explore the other pillars

Put the discipline into practice — in paper first.

Start in paper mode, validate with walk-forward backtests, and let the risk engine hold the line. No real capital is at risk until you decide to connect Kraken.

No profit promises. Paper trading by default.