One trade per team per coin
Each of your teams can hold only one open position on a coin at a time. If Agent A opens a trade on BTC for your Main team, Agents B and C on Main wait until that trade closes — they cannot pile into the same coin on the same team.
This prevents multiple agents from stacking conflicting positions on a single coin in one account. Each team is its own trading account, so different teams can each hold their own position on the same coin — even in opposite directions.
Quick start: what happens when agents compete
You have two agents on BTC:
| Rule | Agent | Order |
|---|---|---|
| 1 | Trend Rider | 1 |
| 2 | Range Scalper | 2 |
Trend Rider opens a long trade at 09:00 UTC. At 10:00, Range Scalper qualifies for a short signal.
What happens: Range Scalper waits. The team already has an open position on the coin. No new trade can open on this team's BTC until Trend Rider's position closes.
How it works
The coin is locked for the team while a position is open
| State | What can happen |
|---|---|
| No position | Any on-duty agent can open a trade |
| Position open | The position owner manages it. Other agents wait. |
| Position closed | After cooldown, any on-duty agent can open a new trade |
The owner keeps the trade, even if rules change
If rules change mid-trade (you edit the setup, or regime/hours shift), the agent that opened the trade keeps it. Radar doesn't reassign positions.
Example: Trend Rider opens a trade during a Bull trend. The regime shifts to a Bear range while the trade is open. Trend Rider still owns and manages the trade — it doesn't get handed to your Bear range agent.
Candle close outcomes
When your agent's strategy candle closes, Radar records what happened:
| Outcome | What it means |
|---|---|
| Traded | The agent opened a trade on this candle close |
| No trade | The agent's strategy didn't qualify — no trade opened |
| Taken by higher rule | The agent qualified, but a lower-numbered rule's agent traded instead |
| Skipped | The candle close was missed due to late data |
| Claimed | Another agent on the same team already holds a position on this coin — your agent waits |
| Missed | The agent qualified but couldn't act in time (rare timing edge case) |
Taken by higher rule
When two agents both qualify on the exact same candle close, Order decides who trades:
- The lower-numbered rule wins
- The other agent's signal is marked Taken by higher rule
- The losing agent's edge is kept for a later candle — it can still trade next time it qualifies
Example: At 14:00 UTC, both Momentum Trader (Order 1) and Scalper (Order 2) qualify. Momentum Trader opens the trade. Scalper sees Taken by higher rule in its activity log.
Skipped
Skipped means Radar couldn't evaluate that candle close because market data arrived late. No measurement was taken.
This is different from No trade (agent evaluated and didn't qualify) or Claimed (another agent on the team holds the coin).
Cooldown between trades
After a trade closes, there's a cooldown period before the team's coin can take another trade. This prevents rapid-fire re-entries after a stop-out or quick close.
| Setting | Sample value | What it means |
|---|---|---|
| Cooldown | 1–5 minutes (admin-configured) | Wait time before the team's next trade on this coin |
Note: The exact cooldown value is configured by BattleGrid administrators and may vary. The UI shows when the cooldown ends.
Why cooldown exists
Without cooldown, a stop-out could immediately trigger a new entry if the agent still qualifies — sometimes right into the same failed move. The pause gives price time to develop and prevents emotional re-entries.
Worked example: Three agents, one coin
You have BTC on Radar for your Main team with:
| Rule | Agent | Conditions |
|---|---|---|
| 1 | Bull Rider | Regime: Bull trend |
| 2 | Scalper | Hours: 13:00–17:00 UTC |
| Default | Steady Bot | (catch-all) |
Timeline
| Time | Event | Outcome |
|---|---|---|
| 08:00 | Regime: Bull range. Steady Bot on duty. | |
| 08:15 | Steady Bot qualifies | Traded — opens long |
| 09:00 | Regime: Bull trend. Bull Rider goes on duty. | |
| 09:15 | Bull Rider qualifies | Claimed — Steady Bot owns the trade |
| 10:00 | Steady Bot's trade closes | Cooldown starts |
| 10:02 | Cooldown ends | |
| 10:15 | Bull Rider qualifies | Traded — opens long |
| 13:00 | Scalper goes on duty (hours match) | |
| 13:15 | Scalper qualifies | Claimed — Bull Rider owns the trade |
| 14:00 | Bull Rider's trade closes | Cooldown starts |
| 14:02 | Scalper qualifies | Traded — opens long |
Key points:
- The team only holds one position on the coin at a time
- Agents queue behind whoever owns the current trade
- After cooldown, whoever qualifies first trades — Order only decides ties
Good to know
-
One position per team per coin, not per agent. If you have 5 agents watching BTC on one team, only one can be in a BTC trade at a time.
-
Teams trade independently. Put BTC on Radar for Main and for Swing, and each team's setup has its own rules, cooldown and position. A trade on Main's BTC never makes Swing's agents wait.
-
Agents on different coins are independent. Agent A trading BTC doesn't block Agent B from trading ETH.
-
The trade owner manages the position. Exit rules, stop-loss, take-profit — all belong to the agent that opened the trade.
-
You can't force a handoff. Even if rules change mid-trade, the original agent keeps the position until it closes.
-
Cooldown is per team and coin. After the team's BTC cooldown ends, the next qualifying agent on that team can trade — doesn't have to be the same agent. Another team's BTC cooldown is its own.
Advanced: Why claimed vs taken by higher rule?
| Outcome | Cause | The agent's signal |
|---|---|---|
| Claimed | Another agent on the team holds a position | Signal discarded — can't act while the team's coin is locked |
| Taken by higher rule | Another agent traded on the same candle close | Signal kept — can trade on a later candle |
Claimed = the team's coin is locked by an existing position. Taken by higher rule = you lost a tie-breaker, but your edge is preserved.
Advanced: Position ownership in edge cases
What if the owning agent is removed from the setup?
The position stays open under the original agent until it closes. Removing an agent from Radar doesn't force-close its open trades.
What if the owning agent is deactivated?
Same behavior — the position remains until closed by the agent's existing exit rules. Deactivation prevents new trades, but doesn't affect open ones.
What about rule-priority changes?
If you edit rule Order numbers mid-trade, the open trade is unaffected. Priority only matters at the moment of opening.
← Radar overview · Rules · Live status