Outway documentation
Project lifecycle
Understand archive, retention and explicit resumable project erasure in Outway.
Archive before erasing
Archive stops new project collection and supports later restoration. Erasure permanently removes eligible project records. Use the API contract to inspect lifecycle version, archive state, active work and deletion preview before choosing an operation. These administrative operations require the appropriate workspace role; scoped AI tools do not erase projects.
Large-project erasure
When staged deletion is enabled, an administrator can submit POST /v1/projects/{projectId}/deletion-task with the exact confirmProjectId, current expectedLifecycleVersion and acceptIrreversibleErasure: true.
Only archived, idle projects qualify. Active or uncertain work can block admission. An accepted task permanently freezes writes and restoration before processing starts. There is no cancel or undo. Repeating the same project/version request returns the existing task rather than starting another erasure.
The worker processes bounded transactions and persists progress between passes. A queued response means accepted work, not completed deletion. Read status with GET /v1/project-deletion-tasks/{taskId}; phase is not a percentage.
Blocked work and retry
Protected cross-project references or database failures can block a task. Earlier committed batches remain erased. Investigate the returned reason before explicitly calling POST /v1/project-deletion-tasks/{taskId}/retry. Retrying does not restore deleted records. There is no automatic retry of blocked failures.
What completion means
Completion removes the selected project’s records and preserves a receipt. Financial costs and admission records are retained. Shared artifact objects and backups have independent storage policies: this operation reports no physical bytes reclaimed. It is not workspace, Identity account or organization deletion.
Automatic retention is separate. It needs both deployment activation and administrator opt-in, processes bounded eligible expired evidence and preserves protected references. An enabled policy is not proof that a production cleanup, backup or restore has succeeded.
Remove expired report payloads
An administrator can preview and explicitly purge eligible model, provider-search and private Google report payloads from an archived, idle project with retention enabled. Plans expire after 15 minutes and contain at most 100 candidates. Running, uncertain or protected shared results are excluded. Confirm the exact phrase shown in the app. Purged history keeps provenance and original request records, with an explicit purged state.
Close a workspace or account
Workspace closure requires all projects erased, Google connections disconnected and payment operations reconciled. Preview the blockers in workspace settings before confirming the workspace ID. Closure preserves a receipt and financial history; it cannot be undone.
Account erasure requires your current password and the exact confirmation phrase in account settings. Transfer sole workspace administration or close those workspaces first. Erasure revokes credentials and sessions and prevents old access tokens from recreating the account.
Physical objects and backups are separate. Operator reclamation verifies eligible tracked objects after a grace period; it does not delete retained backups, versioned objects or all historical orphaned files. Account/workspace erasure is not a promise that every retained financial record or downloaded copy disappears.
Automatic expired report cleanup
The retention policy has separate consent for automatic report payload cleanup (automaticReportPurge) and capture cleanup (automaticPurge). Neither consent implies the other. Automatic cleanup also requires operator activation, enabled retention and an archived, idle project.
Each hourly pass clears at most 100 expired terminal report payloads. Shared reports, uncertain requests and referenced audit, SERP or automatic-review evidence are protected. Requests and financial history remain. Physical objects, historical orphan inventories and backups require their separate storage lifecycle procedures. You can still preview and explicitly purge eligible report payloads without enabling automatic cleanup.