手动触发 cron 报 pairing required：先隔离“调度可跑、CLI 失败”的 scope-upgrade 场景
问题/场景：`openclaw cron run <id>` 或 CLI 发起 `sessions_spawn` 时出现 `pairing required ... scope-upgrade`，但定时调度仍可执行。前置条件：本地 gateway 使用 token 鉴权，且已能复现实例。实施步骤：先确认同一作业在 scheduler 路径能成功，再核对 token/会话身份并用最小命令重试，最后收集日志与环境信息提交 issue。关键命令：`openclaw cron run <id> --expect-final --timeout 120`、`openclaw gateway status`。验证：CLI 手动触发恢复成功且不再报 1008。风险与边界：不要在定位前盲目清理全部配对，避免影响线上节点。来源：Issue #22275。
GITHUBDiscovered 2026-02-21Author openclaw community
Prerequisites
- OpenClaw version is near 2026.2.19-2 and gateway auth mode is token on loopback/local setup.
- You can run both scheduler path and manual CLI path for the same cron job.
Steps
- Run the job in normal scheduler flow first to confirm backend execution path is healthy.
- Immediately run manual trigger (`openclaw cron run <id> --expect-final --timeout 120`) and compare error signature.
- Check gateway auth/token consistency and capture `openclaw gateway status` output plus relevant logs.
- If mismatch persists, keep scheduler running as temporary mitigation and submit reproducible environment details to issue tracker.
Commands
openclaw cron run <id> --expect-final --timeout 120openclaw gateway statusopenclaw gateway restartVerify
Manual CLI triggers complete without `pairing required` while scheduler/manual outcomes stay consistent.
Caveats
- Issue remains open; fixes and exact root cause may change by release (需验证).
- Do not rotate/remove production tokens blindly when only manual trigger path is affected.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗