> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voqo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan multiple War Room signals safely

> Select, queue and track related signals as one coordinated planning flow without creating duplicate tasks.

# Plan multiple War Room signals safely

The War Room can coordinate several signals for the same contact while showing
one clear planning flow. This prevents a task from being executed before all
related planning has finished.

## Before you begin

* Open **War Room** and choose the **Pipeline** view.
* You need a Workspace Admin or Member role to plan, retry or cancel work.
  Viewers can follow progress and open history, but cannot make changes.
* Each signal must have a contact and a completed plan.

## Plan several signals together

1. In the **Signal** column, tick up to 20 signals for one contact.
2. Check the selected count and contact name above the board.
3. Select **Plan selected**.

The **Task** column shows one planning card. Its progress changes from
**Planning 1 of 3** as each signal is processed. Signals are sent for planning
one at a time. Task execution stays unavailable until planning and any queued
work for that contact are resolved.

You can also drag a signal into the **Task** column. If planning is already in
progress, the signal is not moved automatically. You must choose what happens
next.

## Add a signal or keep it separate

When the contact already has active planning, choose one of these options:

* **Add to current planning** places the signal at the end of the active
  planning flow. You can also drag it directly onto the active planning card.
* **Keep separate and plan next** creates a visible queued card. The card keeps
  its queue position and starts only after earlier planning is resolved.

For keyboard use, tick the signal and use the matching button above the board
or **Add selected here** on the active card.

## Read planning progress

Each source row shows one of these states:

* **Waiting** — the signal is in sequence and has not been sent yet.
* **Processing** — the signal is being planned or awaiting confirmation.
* **Complete** — its result has been reconciled.
* **Retry available** — the request is known to be safe to send again.
* **Confirmation unknown** — AgentOS may already have accepted the signal.

If all signals return the same task ID, the board shows one task card with its
combined source count. If they return different task IDs, the board keeps them
as separate tasks and records why the planning flow split.

Open **History** on a task to review its sources and applied updates. Older
tasks show history only from the date this feature was enabled.

## Recover when planning needs attention

* If **Retry** is shown, you can safely retry the affected source.
* If the card says AgentOS may have accepted the signal, wait for confirmation
  or select **Cancel planning**. Retry is deliberately unavailable because it
  could create duplicate work.
* Cancelling an active group keeps tasks that were already resolved, releases
  unresolved signals and allows the next queued group to proceed.
* Cancelling a queued group removes only that group and keeps the remaining
  queue order.

The card displays the exact reason for a failure. If an unknown problem shows a
correlation ID, include that ID, your workspace ID and a screenshot when you
contact support.

## Limits and common messages

* Select signals for one contact at a time.
* A group can contain up to 20 signals.
* A contact can have up to 10 queued groups and 100 queued signals.
* If a signal or task changed in another tab, refresh the board and choose
  again. Your previous command will not be applied silently.
* A task cannot be moved to **Execute** while its contact has active planning,
  queued planning or an unresolved update conflict.

## Expected result

You can see one coordinated planning card, make an explicit decision for rapid
new signals, follow the queue, and understand whether retry or cancellation is
safe. Related updates to one task remain together with a complete history;
different tasks remain separate.

## Related docs

* [Permission denied or feature unavailable](../troubleshooting/permission-denied-or-feature-unavailable)
* [Troubleshooting hub](../troubleshooting/index)