Files
openclaw/qa/scenarios/scheduling/cron-execution-diagnostics.yaml
2026-08-04 05:29:13 +08:00

32 lines
1.4 KiB
YAML

title: Cron execution diagnostics
scenario:
id: cron-execution-diagnostics
surface: automation
category: automation.cron-jobs
coverage:
primary:
- automation.model-provider-preflight
- automation.timeout-and-denial-diagnostics
objective: Prove isolated cron runs persist and expose provider preflight, timeout, and execution-denial diagnostics.
successCriteria:
- A real loopback transport failure is rejected by the production isolated-run model-provider preflight before agent execution.
- The provider-preflight skip is persisted in cron task history and emitted as an operator-visible finished event.
- A terminal command-lane timeout is normalized, persisted, and emitted with its canonical cron diagnostic.
- A fatal typed execution denial is normalized, persisted, and emitted with its tool diagnostic.
docsRefs:
- docs/automation/cron-jobs.md
- docs/cli/cron.md
- docs/gateway/protocol.md
codeRefs:
- src/cron/isolated-agent/model-preflight.runtime.ts
- src/cron/isolated-agent/run.ts
- src/cron/isolated-agent/run-finalize.ts
- src/cron/service/timer-execution.ts
- src/cron/task-run-history.ts
- src/cron/cron-execution-diagnostics.e2e.test.ts
execution:
kind: vitest
path: src/cron/cron-execution-diagnostics.e2e.test.ts
summary: Run real CronService jobs through isolated-run preflight and terminal diagnostic persistence boundaries.