Operations and asynchronous work
Track accepted work, partial execution, cancellation, deadlines, and safe retries.
An operation records work accepted by the control plane. Acceptance is separate from the resulting policy adoption, report availability, scan result, or response acknowledgement.
Open Organization → Activity → Operations or select the operation link returned by a feature's action. Inspect its target IDs, phases, start and finish times, and result before starting dependent work.
| State | Meaning |
|---|---|
queued | Accepted and waiting for an executor |
running | Execution has begun; effects might already exist |
succeeded | The operation's documented completion condition was met |
failed | Work ended with an error; inspect partial results |
canceled | Further cancelable work stopped; committed effects remain |
expired | Work did not begin before its execution deadline |
Partial outcomes
Open the operation's target results to see succeeded, failed, or skipped with a reason for each target. A required target failure makes the aggregate operation fail. After correcting the reported cause, submit replacement work for the failed targets only; successful targets do not need the same action again.
The completion check depends on the operation:
| Operation | What success confirms | What to check next |
|---|---|---|
| Policy publication | The revision and assignments were recorded | Policies → Policy → Adoption for each executor's applied revision |
| Response execution | The executor acknowledged the requested effect | The action's per-target result and the target's observed response state |
| Report generation | The report artifact is available | Reports → Report → Downloads for its cutoff and coverage |
Cancel and retry
Open Organization → Activity → Operations, select the operation, and check cancelable. If it is true, choose Cancel and wait for succeeded, failed, canceled, or expired. Execution can finish before cancellation takes effect, so inspect the completed target results even if the cancellation request was accepted.
If cancelable is false, the current step cannot be interrupted. Follow its result before starting another action against the same target. A completed quarantine or isolation remains applied; use quarantine restoration or Release isolation when recovery is required.
A browser timeout stops waiting, not execution. Store the returned operation ID. For an ambiguous API write, repeat the original request with the same idempotency key. If its retention window has elapsed, inspect current resource state before issuing new work.
Response actions add approval and expiry states described in response actions. A queued action that expired must be re-evaluated and requested again; reconnecting an old agent must not execute it. Use Operation API for polling and cancellation.