Bot Statuses And Status Reason
The dashboard does not only show whether a bot exists. It shows the bot's current runtime state, and that state determines whether you should launch, wait, inspect, or intervene.
What this is
This article explains the main bot statuses and the extra signals that refine what a paused bot actually means.
When to use it
Use this article if:
- you see a status on the dashboard and do not know what action it implies
- a bot appears paused and you need to know why
- you want to understand the difference between runtime status and warning chips
Before you start
Important behavior:
- the dashboard uses clear labels such as Awaiting Signal , In Position , Awaiting Stop , and Stop
- some paused states include extra context, such as low balance or a required re-check
- a missing or stale backtest can also appear as a separate warning
Step by step
Step 1: Read running states correctly
When a bot is running, the dashboard usually shows one of these labels:
- Awaiting Signal
- In Position
That difference comes from whether the bot is currently managing an open position.
Step 2: Read paused states through the extra context shown on the row
Paused does not always mean the same thing.
The current dashboard can render paused bots as:
- Awaiting Stop
- Insufficient Balance
- Position Closed Externally
- a configuration-change state that means a fresh backtest is needed
These states imply different next actions.
Step 3: Treat configuration-change pauses as a revalidation signal
If the bot was edited in a strategy-affecting way, SteadyEdge can pause it and require a fresh backtest before you rely on launch again.
That means:
- the current config no longer matches the old backtest
- the bot needs a fresh backtest before launch should be trusted again
Step 4: Treat stop and error differently
- Stop means the bot is not running
- Error means something went wrong and the bot needs inspection
Do not restart an error-state bot blindly. Check the related exchange account, balance context, and recent actions first.
Step 5: Notice warning chips that are not statuses
The dashboard can also show warnings such as:
- the bot still needs a backtest
That warning is operationally important, but it is not the same as the runtime status. Read both together.
What you should see
After reading the dashboard row, you should be able to answer:
- is the bot actively trading
- is it in a position or waiting for one
- if paused, why is it paused
- whether the next action should be start, wait, inspect, top up, or re-backtest
Common mistakes
- reading every paused bot as the same situation
- confusing a backtest warning with a runtime error
- restarting a bot without understanding why it paused
- assuming a running bot always has an open position
- treating an external position close as a normal stop
Related articles
- Save, Edit, Clone, And Launch
- Why Backtest Is Required Before Launch
- Trade Journal And Export