docs: fix TaskFlow CLI command path and CLI task notify policy

This commit is contained in:
Vincent Koc
2026-04-03 03:03:00 +09:00
parent 9f3a26caa6
commit bcd61e54e1
6 changed files with 28 additions and 54 deletions

View File

@@ -56,7 +56,7 @@ See [Cron vs Heartbeat](/automation/cron-vs-heartbeat) for a detailed comparison
## TaskFlow
[TaskFlow](/automation/taskflow) is the flow orchestration substrate above background tasks. It manages durable multi-step flows with managed and mirrored sync modes, and exposes `openclaw flows list|show|cancel` for inspection and recovery. See [TaskFlow](/automation/taskflow) for details.
[TaskFlow](/automation/taskflow) is the flow orchestration substrate above background tasks. It manages durable multi-step flows with managed and mirrored sync modes, and exposes `openclaw tasks flow list|show|cancel` for inspection and recovery. See [TaskFlow](/automation/taskflow) for details.
## Related

View File

@@ -2,7 +2,7 @@
summary: "TaskFlow flow orchestration layer above background tasks"
read_when:
- You want to understand how TaskFlow relates to background tasks
- You encounter TaskFlow or openclaw flows in release notes or docs
- You encounter TaskFlow or openclaw tasks flow in release notes or docs
- You want to inspect or manage durable flow state
title: "TaskFlow"
---
@@ -26,26 +26,26 @@ Each flow persists its own state and tracks revisions so progress survives gatew
```bash
# List active and recent flows
openclaw flows list
openclaw tasks flow list
# Show details for a specific flow
openclaw flows show <lookup>
openclaw tasks flow show <lookup>
# Cancel a running flow
openclaw flows cancel <lookup>
openclaw tasks flow cancel <lookup>
```
- `openclaw flows list` — shows tracked flows with status and sync mode
- `openclaw flows show <lookup>` — inspect one flow by flow id or lookup key
- `openclaw flows cancel <lookup>` — cancel a running flow and its active tasks
- `openclaw tasks flow list` — shows tracked flows with status and sync mode
- `openclaw tasks flow show <lookup>` — inspect one flow by flow id or lookup key
- `openclaw tasks flow cancel <lookup>` — cancel a running flow and its active tasks
## How flows relate to tasks
Flows coordinate tasks, not replace them. A single flow may drive multiple background tasks over its lifetime. Use `openclaw tasks` to inspect individual task records and `openclaw flows` to inspect the orchestrating flow.
Flows coordinate tasks, not replace them. A single flow may drive multiple background tasks over its lifetime. Use `openclaw tasks` to inspect individual task records and `openclaw tasks flow` to inspect the orchestrating flow.
## Related
- [Background Tasks](/automation/tasks) — the detached work ledger that flows coordinate
- [CLI: flows](/cli/flows) — CLI command reference for `openclaw flows`
- [CLI: tasks](/cli/index#tasks) — CLI command reference for `openclaw tasks flow`
- [Automation Overview](/automation) — all automation mechanisms at a glance
- [Cron Jobs](/automation/cron-jobs) — scheduled jobs that may feed into flows

View File

@@ -59,7 +59,7 @@ openclaw tasks audit
| ACP background runs | `acp` | Spawning a child ACP session | `done_only` |
| Subagent orchestration | `subagent` | Spawning a subagent via `sessions_spawn` | `done_only` |
| Cron jobs (all types) | `cron` | Every cron execution (main-session and isolated) | `silent` |
| CLI operations | `cli` | `openclaw agent` commands that run through the gateway | `done_only` |
| CLI operations | `cli` | `openclaw agent` commands that run through the gateway | `silent` |
Main-session cron tasks use `silent` notify policy by default — they create records for tracking but do not generate notifications. Isolated cron tasks also default to `silent` but are more visible because they run in their own session.
@@ -226,9 +226,9 @@ A sweeper runs every **60 seconds** and handles three things:
### Tasks and TaskFlow
[TaskFlow](/automation/taskflow) is the flow orchestration layer above background tasks. A single flow may coordinate multiple tasks over its lifetime using managed or mirrored sync modes. Use `openclaw tasks` to inspect individual task records and `openclaw flows` to inspect the orchestrating flow.
[TaskFlow](/automation/taskflow) is the flow orchestration layer above background tasks. A single flow may coordinate multiple tasks over its lifetime using managed or mirrored sync modes. Use `openclaw tasks` to inspect individual task records and `openclaw tasks flow` to inspect the orchestrating flow.
See [TaskFlow](/automation/taskflow) and [CLI: flows](/cli/flows) for details.
See [TaskFlow](/automation/taskflow) for details.
### Tasks and cron
@@ -257,5 +257,5 @@ A task's `runId` links to the agent run doing the work. Agent lifecycle events (
- [Cron Jobs](/automation/cron-jobs) — scheduling background work
- [Cron vs Heartbeat](/automation/cron-vs-heartbeat) — choosing the right mechanism
- [Heartbeat](/gateway/heartbeat) — periodic main-session turns
- [CLI: flows](/cli/flows) — CLI reference for `openclaw flows`
- [CLI: tasks](/cli/index#tasks) — CLI reference for `openclaw tasks flow`
- [CLI: Tasks](/cli/index#tasks) — CLI command reference