How-to guide · Kraken API Trading Bot

How to Read the Execution Audit Trail

Every order, signal, and rejection is logged in order — here is how to read the audit trail and confirm the bot did exactly what it should.

Published June 7, 2026 · Primary topic: execution audit trail

← Back to the Kraken API Trading Bot hub

Automation is only trustworthy if it is accountable. The execution audit trail is the bot's complete, chronological record of what it did and why — every signal it evaluated, every order it placed, and every signal it refused. Learning to read it turns "the bot traded" into "the bot traded for these specific, checkable reasons."

What the audit trail records

The trail is append-only and time-ordered. For each moment of decision it captures the signal that was considered, the cost check that was run against it, the resulting action — an order or a rejection — and the outcome once the exchange responds. Nothing the bot does happens off the record.

Step by step

  1. Open the audit trail. Find the chronological log of every action, from signal evaluation through to order outcome. Read it top to bottom; sequence is part of the story.
  2. Trace a single signal. Follow one signal from generation, through its cost check, to either a placed order or a logged rejection. This end-to-end view is how you confirm the rules fired correctly.
  3. Read the rejections. Rejections record why a signal failed the cost bar. These are working-as-intended entries, not faults — a quiet day of rejections is the discipline doing its job.
  4. Reconcile orders to fills. Match each placed order to its fill and to any risk event, so every order has a beginning and an end you can account for.

Using the trail as a tool, not a receipt

The audit trail is most valuable read forward, not just looked up after something goes wrong. Reviewing it regularly tells you whether the bot is rejecting weak signals as expected, whether fills are landing near the prices the cost model assumed, and whether risk limits are intervening when they should. It is also the first place to look after any unexpected event.

The same log is where you start a recovery: see how to recover the bot after a kill switch. To understand the rejections you will read here, the signals pillar explains the cost-beating rule, and paper mode vs live mode covers how the same trail behaves before and after you go live.

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.