Reference
Statuses and outcomes
Check the customer-facing meaning of readiness, action, agent, journey, run, check, finding, cleanup, export, and notification states.
| State | Meaning |
|---|
| Ready | Required evidence, coverage, and safety conditions are satisfied |
| Needs attention | A problem, gap, or stale result requires review |
| Not ready | A required condition failed or cannot be verified |
| State | Meaning |
|---|
| Ready | Approved information supports safe assessment use |
| Needs setup | Required action information or connection state is incomplete |
| Archived | Kept for history and excluded from new assessments |
| State | Meaning |
|---|
| Active | Available for new assessments |
| Ready to activate | Compatibility checks passed and activation remains |
| Inactive | Paused or unavailable for new work |
| Archived | Kept for historical results only |
| State | Meaning |
|---|
| Draft | Editable and not yet approved |
| In review | Waiting for an approval decision |
| Approved | Eligible to run when dependencies are ready |
| Superseded | Replaced by a later approved version |
| Withdrawn | Removed from approval or future use |
| State | Meaning |
|---|
| Created | The run record exists |
| Queued | Waiting to dispatch |
| Dispatching | Preparing execution |
| Running | The agent is working |
| Waiting | Paused for a defined delay or retry condition |
| Verifying | Checking product state |
| Cleaning up | Restoring or removing temporary state |
| Cancel requested | Queued work has a pending cancellation |
| Stop requested | Active work has a pending safe-stop request |
| Completed | Execution, verification, and required cleanup reached a terminal result |
| Canceled | Work ended before starting ordinary execution |
| Stopped | Active work ended through a safe-stop request |
| Failed | Execution failed with a known terminal failure |
| Indeterminate | Invokeable cannot determine a trustworthy terminal result |
| Outcome | Meaning |
|---|
| Passed | The expected state and protected behavior were verified |
| Needs attention | One or more meaningful checks failed or a problem was found |
| Couldn't complete | The run stopped, failed, became invalid, or lacked enough trustworthy evidence |
Open the run to see the checks that produced the outcome. The summary keeps the result short, while the checks explain incomplete work, unsafe behavior, incorrect changes, failed recovery, missing evidence, and other reasons the run did not pass.
| Result | Meaning |
|---|
| Passed | Supporting evidence confirms the expected behavior |
| Failed | Evidence shows that the expected behavior was not met |
| Inconclusive | Evidence is missing, conflicting, inaccessible, or unavailable |
| State | Meaning |
|---|
| Open | New problem awaiting triage |
| Investigating | Evidence and cause are under review |
| Needs evidence | The decision requires more trustworthy evidence |
| Confirmed | The problem is sufficiently supported |
| Remediating | A fix is being prepared or executed |
| Verifying | A later assessment is checking the fix |
| Resolved | The expected behavior was verified after remediation |
| Intentional | The observed behavior is accepted as intended |
| Merged | The record was combined with another finding |
| State | Meaning |
|---|
| Not required | The run created no temporary state requiring cleanup |
| Pending | Cleanup is waiting to start |
| Running | Cleanup is in progress |
| Verified | The environment was confirmed restored |
| Failed | Cleanup did not restore the expected state |
| Indeterminate | Restoration could not be confirmed |
Requested, processing, ready, failed, expired, and revoked describe the export lifecycle. Only a ready, unexpired, unrevoked export can produce a temporary download URL, subject to current authorization.
Notifications can be unread or read. Delivery channels can be pending, delivering, delivered, failed, or suppressed. A failed email does not remove the in-product notification.
