Save, Edit, Clone, And Launch
Building a bot is not the same as launching it. A bot moves through several practical stages: saved configuration, backtested candidate, and live runtime.
What this is
This article explains how SteadyEdge handles saving, editing, cloning, starting, pausing, stopping, and deleting bots.
When to use it
Use this article if:
- you finished configuring a bot and want to know what happens next
- you are editing an existing bot from the dashboard
- you want to clone a ready bot or understand the launch controls
Before you start
Before launching any bot, remember these rules:
- saving a new bot and updating an existing bot both return you to the dashboard
- starting a bot requires verified email, a passed backtest, and positive available balance
- if a config change affects the strategy, SteadyEdge clears backtest_passed
- if a running bot is paused while it has an open position, the stop flow becomes position-aware
Step by step
Step 1: Save the bot as a reusable configuration
When you click Save Bot :
- a new bot is created if this is the first save
- an existing bot is updated if you are editing
The save step matters because the backtest and start flows operate on a saved bot record.
Step 2: Edit the bot when strategy logic changes
Use Edit when you want to change:
- core market context
- filters
- grid
- exits
- risk
If the change affects what the bot would do, treat the previous backtest as stale.
Step 3: Understand what cloning really does
SteadyEdge supports cloning from public ready bots and completed public backtests that are exposed as ready strategies.
Use cloning when:
- you want a faster starting point
- you want to adapt a public setup to your own exchange, capital, or risk rules
A clone is still your own bot and should be reviewed and backtested again before launch.
Step 4: Launch only after the gate is clear
The start flow checks three critical things:
- your email is verified
- the bot has passed a backtest
- your available balance is above zero
If any of those fail, the bot does not start even if the configuration itself is valid.
Step 5: Use the correct stop action
If the bot is running and not in a position, stopping is straightforward.
If the bot is already in a position, the pause modal offers two different actions:
- Close position now and stop bot
- Wait for position to close, then pause bot
These map to different engine commands and should not be treated as the same kind of stop.
Step 6: Know the delete rules
Deletion is intentionally restricted. SteadyEdge will not delete a bot if:
- it is still running
- it still has an open position
That protects runtime state and trade history from being removed at the wrong time.
What you should see
At each stage, you should see a clear result:
- after save: the bot appears on the dashboard
- after edit: the updated bot returns to the dashboard
- after clone: you get an editable copy
- after start: the row moves into a live runtime state
- after stop or pause: the dashboard reflects the new state
Common mistakes
- treating a saved draft as launch-ready
- cloning a public bot and skipping validation and backtesting
- forgetting that launch checks available balance, not bonus balance
- editing strategy logic but relying on an old backtest
- trying to delete a bot that is still running or still in position
Related articles
- Why Backtest Is Required Before Launch
- Bot Statuses And Status Reason
- How To Read Backtest Report
- Trade Journal And Export