Commands Still Waiting
Account → Commands still waiting lists the AI commands you started that reached a device but whose result never came back.
Why this page exists
When the AI assistant runs a command that changes a device's state on your behalf, the manager records it as a durable task and waits for the device to report the result. Until that result arrives, the conversation is held read-only — no second state-changing command may go out, because the first one may still be running on the device.
Almost always the result arrives within seconds and this page is empty. But there are cases where it never arrives:
- the device went offline, shut down, or rebooted mid-run;
- the command itself hung, neither returning nor timing out;
- the link between the device and the manager dropped and never recovered.
The conversation would then stay read-only indefinitely. This page is where you clear it.
What the statuses mean
| Status | Meaning |
|---|---|
| Sent | The command reached the device and the manager is still waiting normally. |
| Outcome unknown | The wait timed out and the manager gave up waiting automatically. This does not mean the command failed — it may well have succeeded on the device, with only the result failing to get back. |
For a state-changing command the manager never resends automatically. Re-running a command that may already have executed is far riskier than leaving it at "outcome unknown".
What "stop waiting" does and does not do
Clicking Stop waiting:
- ✅ lifts the read-only hold, so you can keep working with the AI on that device;
- ✅ records when you decided to stop waiting;
- ❌ does not mean the command succeeded;
- ❌ does not mean the command failed;
- ❌ does not cancel a command that may still be running on the device.
The distinction is deliberate. All you can judge is that waiting longer is pointless; you cannot know what the device actually did. So the action releases the wait without drawing a conclusion on the device's behalf.
If the device does report later, the real result is still recorded in full. It is neither overwritten nor discarded by your action — which is what makes stopping safe: you lose no real information by doing it.
What "cancel command" does
"Stop waiting" only touches your side of the conversation and leaves the device alone. Cancel command goes further: it tells the device to stop running the command.
Clicking Cancel command (with a confirmation prompt) leads to one of two outcomes, depending on how far the command has got:
- It has not actually started yet (still in approval / dispatch): the manager marks it cancelled in place, the device never runs it, and the UI reports the command was cancelled;
- It may already be running on the device: the manager records the cancel as a durable desired state, and a background reconciler then delivers the request to the device, which aborts as soon as it receives it. The UI reports cancel requested; notifying the device.
Cancelling is idempotent and safe:
- once recorded, the cancel keeps being delivered until the device acknowledges — unaffected by a manager instance switching over or restarting mid-way;
- if the device ultimately reports that the command had in fact already finished, the real result is still recorded faithfully rather than forced to "cancelled";
- if the command really is stopped before or during its run, the read-only hold on that conversation is lifted too, so you need not also click "stop waiting".
Which should you use? Just want your own conversation unblocked and don't care about the device's command → Stop waiting; want the device to actually not run the command → Cancel command.
What to do first
Before you stop waiting, try to establish what the command actually did:
- Connect to the device with remote desktop and check whether the command took effect (was the service restarted, was the file changed);
- If the device is offline, wait for it to come back — a reconnecting device may still report the result, and the entry will disappear from this page on its own.
Only once you are satisfied that waiting is pointless should you click Stop waiting.
Who can see what
This page shows only the commands you started. You cannot see or act on anyone else's, and neither can an administrator — only the person whose conversation is held can release it.