Live status and activity
Radar's live status shows what's happening right now on each coin. The activity log shows what happened recently — last 10 events and top reasons over the past 7 days.
Quick start: reading the status
Open your Radar dashboard and look at the status column for each coin:
| Status | What it means | Action needed |
|---|---|---|
| Scanning | An agent is on duty and watching | None — working normally |
| In position | A trade is currently open | None — trade in progress |
| Idle | No agent is on duty | Check your rules |
Tip: If you see Idle when you expected trading, check Why isn't Radar trading?
All status values
Primary statuses
| Status | What it means |
|---|---|
| Scanning | At least one agent is On duty and watching for a trade opportunity |
| In position | A trade is currently open on this coin |
| Idle | No agent is on duty — rules don't match and there's no default agent |
| Paused | You paused this Radar setup |
Blocking statuses
These show why Radar can't proceed normally:
| Status | What it means | What to do |
|---|---|---|
| No regime reading yet | Waiting for the first closed candle to read the regime | Wait for the next candle close |
| All agents filtered | Every agent in the setup is inactive or ineligible | Reactivate an agent |
| Paused by BattleGrid | Platform maintenance in progress | Wait — resumes automatically |
| Entries paused | New entries temporarily blocked (usually a market data gap) | Wait — resumes automatically |
| Policy disabled | The Radar setup for this coin is currently off | Enable the setup or check settings |
What's blocking: detailed reasons
When Radar shows a blocking status, expand the coin row to see the specific reason:
| Reason | Explanation |
|---|---|
| No rule match | No rule's conditions are true and there's no default agent |
| Regime not available | Waiting for closed candle data on the regime timeframe |
| Volatility not in this rule | The regime matches, but the rule only lists some volatility levels and the current one isn't among them |
| Paused — the reading carries a warning | The regime matches, but the rule is set to Pause during warnings and a warning (Crash or Momentum divergence) is active |
| Runs only during warnings — none holds | The regime matches, but the rule is set to Only during warnings and no warning is active |
| Hours outside | Current UTC time is outside all rules' trading hours |
| Agent inactive | The matched rule's agent is deactivated |
| Confidence below floor | Agent qualified but confidence was below the rule's minimum |
| Cooldown active | Previous trade just closed — waiting before next entry |
Ready to trade
Ready to trade means an on-duty agent's strategy conditions are met and it could open a trade on the next qualifying candle close.
| State | What it means |
|---|---|
| On duty | The agent is active on this coin because a rule matched (or it's the default) |
| Ready to trade | On duty AND the strategy would qualify for a trade right now |
An agent can be On duty but not Ready to trade if its strategy conditions haven't been met yet.
Activity log
The activity log shows recent events for each coin:
Last 10 events
The 10 most recent candle-close outcomes:
| Event type | What it means |
|---|---|
| Traded | Agent opened a trade |
| No trade | Strategy didn't qualify |
| Taken by higher rule | Another agent with a lower rule number won |
| Skipped | Candle close missed due to late data |
| Claimed | Another agent holds the position |
| Missed | Agent qualified but couldn't act in time |
Top reasons (last 7 days)
A summary of why Radar didn't trade, aggregated over the past week:
| Reason | Example count | What it tells you |
|---|---|---|
| No trade | 142 | Strategy rarely qualifies |
| Claimed | 38 | Other agents often hold the coin |
| Taken by higher rule | 12 | Lower-priority rules occasionally lose ties |
| Skipped | 3 | Rare data gaps |
Use this to understand patterns. If "Claimed" is high, your agents are competing for the same coin. If "No trade" dominates, your strategies may be too selective.
Radar summary
The summary panel shows your overall Radar status:
| Metric | What it shows |
|---|---|
| Coins active | How many coins have Radar setups running |
| Coins limit | Maximum coins you can add to Radar (platform-configured) |
| Positions open | How many coins currently have an open trade |
| Agents on duty | Total agents actively watching across all coins |
Coin limit
You can only have so many coins on Radar at once. The limit is configured by BattleGrid administrators and shown in your dashboard.
| If you hit the limit... | What to do |
|---|---|
| Can't add a new coin | Remove a coin you're not actively trading |
| Need more capacity | Check if higher tiers have larger limits |
Worked example: Interpreting live status
You have BTC and ETH on Radar:
| Coin | Status | Agent | Details |
|---|---|---|---|
| BTC | In position | Trend Rider | Long from $42,150 |
| ETH | Idle | — | No rule match |
What this tells you
- BTC: Trend Rider opened a trade. No other agent can trade BTC until this position closes.
- ETH: No rules matched and there's no default agent. Check your rule conditions or add a default.
Expanding the ETH row
Details panel shows:
| Field | Value |
|---|---|
| Current regime | Bear range · Contracting |
| Current time | 06:15 UTC |
| Rule 1 | Requires Bull trend — not matched |
| Rule 2 | Requires 08:00–16:00 UTC — not matched |
| Default agent | Not configured |
Fix: Add a default agent, or create a rule that matches the Bear range regime.
Good to know
-
Status updates at each candle close. Live status reflects the most recent evaluation, not real-time tick-by-tick.
-
Multiple agents can be "On duty" at once. If rules 1 and 3 both match, both agents are on duty — but only one can trade (see One trade per team per coin).
-
"Entries paused" is temporary. BattleGrid pauses new entries during market data gaps to avoid trades based on stale data. It resumes automatically when data normalizes.
-
Activity log helps debug. If your agent isn't trading, the activity log shows why — "Claimed" means another agent on the team holds the coin, "No trade" means the strategy didn't qualify.
-
Idle isn't always bad. If you want certain regimes only, Idle during other regimes is expected. Idle is a problem only if you expected trading.
Advanced: Status update timing
Radar evaluates status at each relevant candle close:
- Candle closes on the agent's strategy timeframe
- Regime is read from the higher timeframe (if a closed candle is available)
- Rules are checked — which match?
- Agents go on/off duty based on rule matches
- On-duty agents evaluate their strategies
- Status updates in the dashboard
Between candle closes, the status shown is from the last evaluation. If you're watching a 1h agent, status updates hourly.
Advanced: When "Entries paused" activates
BattleGrid pauses new entries when:
- Market data stops arriving for a coin
- Exchange reports connectivity issues
- Significant price data gaps are detected
During the pause:
- Open positions continue to be managed
- Exit rules still trigger
- No new entries are allowed
When data normalizes, entries resume automatically. You'll see this transition in the activity log.
← Radar overview · One trade per team per coin · Troubleshooting