vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 14:20:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(tasks): terminalize gateway agent run ledger

Browse Source 
Terminalize Gateway-backed async task records from the run result while preserving aborted, failed, cancelled, and lost outcomes.\n\nThanks @likewen-tech.
This commit is contained in:
likewen-tech
2026-04-26 12:06:33 +08:00
committed by GitHub
parent f9c8a5107c
commit 86328585fa
13 changed files with 474 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/automation/tasks.md
View File

@@ -115,12 +115,23 @@ stateDiagram-v2
Transitions happen automatically — when the associated agent run ends, the task status updates to match.
Agent run completion is authoritative for active task records. A successful
detached run finalizes as `succeeded`, ordinary run errors finalize as
`failed`, and timeout or abort outcomes finalize as `timed_out`. If an operator
already cancelled the task, or the runtime already recorded a stronger terminal
state such as `failed`, `timed_out`, or `lost`, a later success signal does not
downgrade that terminal status.
`lost` is runtime-aware:
- ACP tasks: backing ACP child session metadata disappeared.
- Subagent tasks: backing child session disappeared from the target agent store.
- Cron tasks: the cron runtime no longer tracks the job as active.
- CLI tasks: isolated child-session tasks use the child session; chat-backed CLI tasks use the live run context instead, so lingering channel/group/direct session rows do not keep them alive.
- CLI tasks: isolated child-session tasks use the child session; chat-backed
CLI tasks use the live run context instead, so lingering
channel/group/direct session rows do not keep them alive. Gateway-backed
`openclaw agent` runs also finalize from their run result, so completed runs
do not sit active until the sweeper marks them `lost`.
## Delivery and notifications