🦞ClawTips
← Back to library

Cron 隔离任务卡死修复：避免 nested lane 死锁（PR #45459）

问题/场景：isolated cron 作业在触发内层队列工作时可能死锁，导致会话未启动就超时。前置条件：使用 sessionTarget=isolated 的 cron agentTurn。实施步骤：1) 升级到 PR #45459；2) 复现会触发内层任务的 cron；3) 连续手动触发并观察 runs；4) 确认不再卡死。关键命令：openclaw cron run / cron runs。验证：作业稳定进入 completed。风险与边界：仅修复 cron→nested lane 映射，其他自定义并发策略仍需压测（需验证）。来源归因：GitHub PR #45459。

GITHUBDiscovered 2026-03-14Author openclaw contributors
Prerequisites
  • You run isolated cron jobs and can inspect run history.
Steps
  1. Upgrade to build containing PR #45459.
  2. Run isolated cron jobs that trigger nested inner work.
  3. Monitor run states for deadlock/timeouts before session boot.
  4. Document safe concurrency limits in your runbook.
Commands
openclaw cron run <jobId>
openclaw cron runs <jobId>
openclaw gateway status
Verify

Isolated jobs complete reliably under repeated runs without nested-lane deadlock.

Caveats
  • Custom hooks with unbounded retries can still cause queue pressure（需验证）.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post