Strategy status
Every strategy status, what it means, and what actions are available in each state.
Every strategy in Coinrule moves through up to 9 distinct lifecycle statuses — from DEPLOYING on first launch through RUNNING, PAUSED, COMPLETED, and ERROR states. Understanding each status tells you what the engine is doing and what action, if any, is required from you.
What are the strategy statuses?
| Status | Description |
|---|---|
| DEPLOYING | Strategy was just launched; the engine is loading it |
| RUNNING | Active — evaluating conditions on each candle |
| PAUSED | Temporarily suspended — won't open new positions but watches for exit conditions |
| STOPPED | Permanently stopped — no evaluation, no orders |
| COMPLETED | All executions done (reached max_open_positions cap and no more entries possible) |
| CLOSING | Completed but an open position remains; exit rules (TP/SL) are still active |
| HOLDING | Completed but an open position remains; no exit rules configured |
| BLOCKED | Engine tripped the consecutive-errors circuit breaker (3+ failures) while a position is open; new opens blocked but exit rules still active |
| ERROR | Fatal error — engine couldn't load or run the strategy |
What is the difference between pausing and stopping?
- Pause — suspends evaluation temporarily. Open positions are not closed. Resume resumes evaluation.
- Stop — permanently terminates the strategy. You can optionally close all open positions at stop time.
Use Pause when you want to temporarily halt a strategy (e.g. during high-volatility news events). Use Stop when you're done with it.
What is the difference between Completed and Stopped?
A strategy transitions to COMPLETED when it has no more entry conditions it can fulfil — typically because max_open_positions was reached and all positions have been closed. A STOPPED strategy was explicitly terminated by the user or by an error condition.
How do I recover from an error?
A strategy in ERROR or BLOCKED state requires manual review. Check the activity feed for the error message. Fix the underlying cause (usually an exchange connection issue) and re-launch if needed.