Step 3 — Preview & Deploy

1. 1
   Identity

   Symbol, broker, direction and session mode. These cannot be changed after deploy — a mistake here means deleting the strategy and starting again.
2. 2
   Ladder cost vs capital

   Compare the "Ladder Cost" row against "Min Required" and your allocation. This is where an under-funded martingale ladder is caught.
3. 3
   Stop loss

   Confirm it says what you intend. "Disabled" is a legitimate choice, but it should be a chosen one.
4. 4
   Trail modes

   Check whether an extending mode is on and whether trail capital is set for it.
5. 5
   Engine

   Python or C++. Both consume the same config, so this is a runtime choice.

1. 1
   Create the bot record

   The API persists the strategy against your account and returns a strategy id. This id is embedded in every client order id the engine generates.
2. 2
   Write the engine config

   The camelCase wizard payload is translated to the engine's snake_case strategy_parameters and published to Dragonfly (and the active config directory). Both engines read this identical schema.
3. 3
   Resolve credentials

   Broker keys are looked up server-side from your saved credentials. No key material passes through the browser.
4. 4
   Start the engine

   The orchestrator picks up the config, instantiates the strategy in a worker slot, and the engine takes the opening market position and places the ladder.
5. 5
   Go live

   Status flips to running and the strategy appears in the terminal's strategy selector with live grid, positions, orders and logs.

• Missing credentials — no key set is saved for the chosen broker. Add it under Manage Brokers and start the strategy again; the record already exists.
• Insufficient margin — the opening market order is rejected. Lower init lots or grid size, or raise capital.
• Symbol not found — the sub-asset or symbol format does not match the venue. Check the instrument against the broker's contract list.
• Session closed — a session-based venue cannot accept orders yet. The engine waits for the open and builds the ladder then.

The bot record survives a failed start, so you can fix the cause and start it again from the dashboard rather than re-entering the whole configuration.

• Open Bot Visuals for the strategy to watch the grid, positions, pending orders and logs live.
• Use the Settings tab there to change behaviour — sizing, spacing, targets, capital, trailing, stop loss — without redeploying.
• Use the Controls tab to pause, resume, rebalance, stop or kill.

• 1.Engines — Python vs C++ — What runs your config
• 2.Strategy Lifecycle — Live edits, commands and restarts
• 3.Capital Allocation — The numbers on this screen