Module 04 | Drive a running mission: pause before cancel

Pair the mission and owner IDs

Every live control in this sitting required --agent-id. Keep both UUIDs together before acting.

Use two PowerShell windows for tail and controls.

Pause is the reversible brake. Resume releases it. Cancel is one-way and belongs last.

Run in your terminal

armaraos mission resume <MISSION_ID> --agent-id <AGENT_UUID> --json

Run in your terminal

armaraos mission timeline <MISSION_ID> --agent-id <AGENT_UUID> --json

An empty timeline means no handoff was recorded. The command still worked.

Run in your terminal

armaraos mission tail <MISSION_ID> --agent-id <AGENT_UUID> --interval-secs 3

Run in your terminal

armaraos mission pause <MISSION_ID> --agent-id <AGENT_UUID> --json

Run in your terminal

armaraos mission cancel <MISSION_ID> --agent-id <AGENT_UUID> --json

Run in your terminal

armaraos mission get <MISSION_ID> --agent-id <AGENT_UUID> --json

Cancelled is final, but its record remains inspectable. Zero work metrics are the honest result.

Check it / read final state

Get the mission, confirm cancelled, and explain why no delegation claim follows from an empty timeline.

Safety note

Use pause while deciding. Cancel only after capturing the mission ID, owner ID, and needed evidence, because cancellation cannot be resumed.

Troubleshooting for this sitting

What you see	Likely cause	What to do
Agent ID required	Owner was omitted.	Add the owner UUID.
Timeline is empty	No handoff occurred.	Preserve the observation.
Tail keeps polling	It is interactive.	Stop with Ctrl+C.
Resume fails after cancel	Cancel is one-way.	Create a new mission only if needed.