openclaw tasks is equivalent to openclaw tasks list.
See Background Tasks for the lifecycle and delivery
model, and its tasks audit section for full finding descriptions.
Usage
Root Options
Subcommands
list
--status blocked to find completed tasks whose result delivery is blocked.
These tasks retain their stored succeeded status and also remain included in
--status succeeded results; JSON task records keep the same stored status and
terminalOutcome fields.
show
notify
cancel
retry
dismiss
audit
cleanupAfter are warnings;
expired or unstamped lost tasks are errors.
--code accepts task codes (stale_queued, stale_running, lost,
delivery_failed, missing_cleanup, inconsistent_timestamps) and additional
Task Flow codes (restore_failed, stale_waiting, stale_blocked,
cancel_stuck, missing_linked_tasks, blocked_task_missing). See
Background Tasks for severity and trigger detail per
code.
maintenance
lost, so completed cron runs do not become
false audit errors just because the in-memory Gateway runtime state is gone.
Offline CLI audit and maintenance are not authoritative for the Gateway’s
process-local cron, CLI, or ACP liveness. They retain active tasks of those
kinds when the local runtime cannot prove completion. Gateway maintenance
marks CLI tasks with a run id/source id lost when their live run context is
gone, even if an old child-session row remains.
When applied, maintenance also prunes cron:<jobId>:run:<uuid> session
registry rows older than 7 days while preserving currently running cron
jobs and leaving non-cron session rows untouched.
flow
openclaw flows command. Both flow show and flow cancel accept a
flow ID or its stable owner key as <lookup>.
flow list --status accepts queued, running, waiting, blocked,
succeeded, failed, cancelled, or lost. See Task Flow
for ownership and lifecycle details.