cli.schedules_arguments
A jadpo schedules command names an action it doesn't have, or a schedule the project doesn't declare.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo schedules lists the schedules, and run, pause, resume and history act on one by its name. Running or pausing the wrong one would do real work, so a name it doesn't know is refused.
What it looks like
A project with no schedules, asked to run one:
jadpo schedules run nightly_digest error nightly_digest isn't a schedule
- reason
- The project declares no schedules.
- next
- Declare one in a domain's
schedules/folder (agent) - rule
- cli.
schedules_ arguments - help
- https://jadpo.
dev/docs/errors/cli. schedules_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
An action it doesn't have is refused with the ones it does:
jadpo schedules stop nightly_digest error stop isn't something jadpo schedules does
- reason
jadpo scheduleslists the schedules, andrun,pause,resumeandhistoryact on one.- next
- Run
jadpo schedules, orjadpo schedules history <name>(agent) - rule
- cli.
schedules_ arguments - help
- https://jadpo.
dev/docs/errors/cli. schedules_ arguments
How to fix it
If the schedule isn't declared yet, declare it in a domain's schedules/ folder, then run it by name:
jadpo schedules run nightly_digestIt runs the schedule once, now.
Related
Markdown for agents: /docs/errors/cli.schedules_arguments.md.Built from Jadpo main at aee2e8f.