Review and test a workflow before Live activation

Workflows and analysis guide by KLINEO Documentation, updated 18 October 2026.

AI can draft a workflow, but its saved nodes, connections and risk settings define the proposed behavior. Current new-workflow controls open Live activation; a draft is not automatically paper traded. Inspect and validate the saved graph, use available simulation evidence, and review the separate production connection, symbol and risk checks before any Live activation. A prior paper run is not universally required by the current activation flow.

Before you start

A KLINEO account with workflow access and enough AI allowance if requesting AI drafting.
A clearly defined exchange, market, symbol, timeframe, trigger and intended action.
No production credentials or live orders are needed merely to read and inspect a draft.

Create a draft you can explain

Example prompt for inspection only: “Draft a BTC spot workflow with an explicit candle-close condition, fixed quote notional and a risk gate; do not activate it.” An AI draft may omit necessary details or choose unsupported settings. Correct the actual node configuration before saving a version.

Open Klineo AI / Agentic Workflow and create a saved blank workflow or an available template.
If using a prompt, describe the market, trigger, conditions, sizing, risk limits and exit behavior explicitly. Wait for drafting to finish before editing or activating.
Inspect every node and edge. Check trigger, data, conditions, risk steps and action nodes; a coherent AI explanation is not validation.
Use Save draft. Review the storage confirmation and saved name so you can return to the same workflow.

Validate and save the version you intend to examine

Open Workflow actions → Validation details. Resolve missing configuration, disconnected paths and unsupported nodes in the actual graph.
Use Save version to create the backend-validated immutable version. A saved draft and a validated version are different states.
Recheck scope and limits after editing. An old validation or simulation result does not prove the current graph has the same behavior.
Keep a record of the version, market, period and costs associated with any result you compare.

Understand the current paper-testing boundary

This guide keeps its paper-workflow URL so existing links remain useful, but the current new-workflow interface is centered on live-funds drafts and an “Activate live” control. Do not click that control expecting a paper order. Historical paper and backtest run records remain readable for compatible saved workflows; their presence does not mean every new draft offers a paper-run button.

Open Workflow actions → Run history & AI review to inspect available run records, and Reports & order history for their evidence. Confirm the run mode and saved version before interpreting a result. Where a compatible legacy paper-run control is actually available, its manual context requires a Candle Close Trigger, exchange, market, symbol, timeframe and a positive reference price. Treat missing context as a blocker.

For a new workflow without a simulation control, retain it as a draft. Use an available backtest tool to investigate a strategy separately and record that it is a different test. Contact support about the supported simulation path rather than substituting Live activation. A backtest on another graph or execution engine does not validate this workflow.

Inspect success, blocked and waiting states

Compare the expected trigger and condition values with recorded node results. A “passed” condition is evidence only for that run’s inputs.
For a blocked or rejected run, read the missing field, unsupported scope, quota or risk reason; do not remove the risk gate just to obtain a passing run.
An approval or waiting state means the action has not necessarily completed. It is not a filled-order receipt.
Compare intended actions with order history and execution receipts when those records exist. A profitable chart is insufficient evidence of the order lifecycle.
Keep simulated, historical and Live records separate when discussing results.

Review Live activation as a separate decision

Confirm the active plan allows a Live workflow slot and that the selected saved workflow and version are eligible.
Open Live activation & recovery. Select the production exchange connection and inspect exact market and symbol eligibility.
Review the current risk policy and maximum-loss preview. Confirm the matching snapshot and accept the Live trading risk disclosure only after understanding its assumptions.
Activate only if you intend real exchange execution. A successful preview or activation request is not a guarantee that every order will fill or that losses are capped.
Inspect run and order records after activation. A prior paper receipt is not a universal activation prerequisite in the current flow.

Use stop controls and verify the result

The workspace exposes Stop live / Kill Switch for an eligible saved workflow. Check the reported state, active orders and positions after using it. Protective reconciliation or already-submitted orders can have their own lifecycle; a paused workflow label is not proof of a flat exchange account.

If you cannot reach KLINEO, inspect and manage exposure directly at the exchange and revoke the API key when necessary. Revoking a key does not itself close an open position.