From 7dc0c57a7ce10d4deb730080eb007fe3d58256fe Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Mon, 27 Apr 2026 08:41:47 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@7d74c29dcc07a49b5639ec7bae1415603a9e3af7 --- .openclaw-sync/source.json | 4 ++-- docs/automation/cron-jobs.md | 2 +- docs/concepts/queue.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index c26844f46..96414a8ee 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "231eb7b52a42a1f2cdfa0e5aba3a0fcd163db1be", - "syncedAt": "2026-04-27T08:39:52.543Z" + "sha": "7d74c29dcc07a49b5639ec7bae1415603a9e3af7", + "syncedAt": "2026-04-27T08:40:23.628Z" } diff --git a/docs/automation/cron-jobs.md b/docs/automation/cron-jobs.md index dfc2396c1..8cf035b86 100644 --- a/docs/automation/cron-jobs.md +++ b/docs/automation/cron-jobs.md @@ -398,7 +398,7 @@ Model override note: } ``` -`maxConcurrentRuns` limits both scheduled cron dispatch and isolated agent-turn execution. Isolated cron agent turns use the queue's `nested` execution lane internally, so raising this value lets independent cron LLM runs progress in parallel instead of only starting their outer cron wrappers. +`maxConcurrentRuns` limits both scheduled cron dispatch and isolated agent-turn execution. Isolated cron agent turns use the queue's dedicated `cron-nested` execution lane internally, so raising this value lets independent cron LLM runs progress in parallel instead of only starting their outer cron wrappers. The shared non-cron `nested` lane is not widened by this setting. The runtime state sidecar is derived from `cron.store`: a `.json` store such as `~/clawd/cron/jobs.json` uses `~/clawd/cron/jobs-state.json`, while a store path without a `.json` suffix appends `-state.json`. diff --git a/docs/concepts/queue.md b/docs/concepts/queue.md index 16524951b..fc92c82b9 100644 --- a/docs/concepts/queue.md +++ b/docs/concepts/queue.md @@ -77,7 +77,7 @@ Defaults: `debounceMs: 1000`, `cap: 20`, `drop: summarize`. - Applies to auto-reply agent runs across all inbound channels that use the gateway reply pipeline (WhatsApp web, Telegram, Slack, Discord, Signal, iMessage, webchat, etc.). - Default lane (`main`) is process-wide for inbound + main heartbeats; set `agents.defaults.maxConcurrent` to allow multiple sessions in parallel. -- Additional lanes may exist (e.g. `cron`, `nested`, `subagent`) so background jobs can run in parallel without blocking inbound replies. Isolated cron agent turns hold a `cron` slot while their inner agent execution uses `nested`; both use `cron.maxConcurrentRuns`. These detached runs are tracked as [background tasks](/automation/tasks). +- Additional lanes may exist (e.g. `cron`, `cron-nested`, `nested`, `subagent`) so background jobs can run in parallel without blocking inbound replies. Isolated cron agent turns hold a `cron` slot while their inner agent execution uses `cron-nested`; both use `cron.maxConcurrentRuns`. Shared non-cron `nested` flows keep their own lane behavior. These detached runs are tracked as [background tasks](/automation/tasks). - Per-session lanes guarantee that only one agent run touches a given session at a time. - No external dependencies or background worker threads; pure TypeScript + promises.