Task Flow Operations

Inspect, cancel, and recover background flows

Page scope (task-flow operations niche): This page targets background orchestration operations only (flow lifecycle, cancellation, recovery). For install/upgrade checklists use Upgrading / Migrating. For deployment rollout use Deployment Upgrade Runbook. For release history use Releases.

Core commands

Task Flow commands
openclaw flows list
openclaw flows show <flow-id>
openclaw flows cancel <flow-id>

Use these commands to observe flow status and manage long-running orchestration separately from interactive chat turns.

Operational checklist

  1. List active flows and identify stalled/blocked states.
  2. Inspect specific flow details before manual intervention.
  3. Cancel only when new scheduling should stop; let active child tasks settle.
  4. Re-run status checks and openclaw doctor to validate final state.

When flows appear stuck

  • Confirm gateway health and provider reachability first.
  • Check whether child tasks are still running before canceling parent flow.
  • After cancellation, verify the flow reaches a terminal state cleanly.

For infrastructure failures, continue in Deployment Upgrade Runbook. For config-path breakages, use Upgrading / Migrating.