mirror of
https://github.com/openclaw/openclaw.git
synced 2026-02-09 05:19:32 +08:00
ab9f06f4ff
- Default one-shot jobs to delete after success, improving job management. - Introduced `--keep-after-run` CLI option to allow users to retain one-shot jobs post-execution. - Updated documentation to clarify default behaviors and new options for one-shot jobs. - Adjusted cron job creation logic to ensure consistent handling of delete options. - Enhanced tests to validate new behaviors and ensure reliability. This update streamlines the handling of one-shot jobs, providing users with more control over job persistence and execution outcomes.
1.1 KiB
1.1 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| CLI reference for `openclaw cron` (schedule and run background jobs) |
|
cron |
openclaw cron
Manage cron jobs for the Gateway scheduler.
Related:
- Cron jobs: Cron jobs
Tip: run openclaw cron --help for the full command surface.
Note: isolated cron add jobs default to --announce delivery. Use --deliver for full output
or --no-deliver to keep output internal. To opt into the legacy main-summary path, pass
--post-prefix (or other --post-* options) without delivery flags.
Note: one-shot (--at) jobs delete after success by default. Use --keep-after-run to keep them.
Common edits
Update delivery settings without changing the message:
openclaw cron edit <job-id> --announce --channel telegram --to "123456789"
Disable delivery for an isolated job:
openclaw cron edit <job-id> --no-deliver
Deliver full output (instead of announce):
openclaw cron edit <job-id> --deliver --channel slack --to "channel:C1234567890"