cli.deliveries_arguments
A jadpo deliveries command names an action it doesn't have, no id for one that needs it, or a state or page it doesn't list.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo deliveries lists the deliveries and schedule runs that need an operator, and retry, dismiss, cancel, resolve, show and abandon act on one. Acting on the wrong one could send something twice or drop it, so each needs the id the list shows.
What it looks like
An action is given no id:
jadpo deliveries retry error jadpo deliveries retry needs an id
- reason
- Each acts on one delivery or schedule run, by the id the list shows.
- next
- Run
jadpo deliveriesto see them, with their ids (agent) - rule
- cli.
deliveries_ arguments - help
- https://jadpo.
dev/docs/errors/cli. deliveries_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
A state it doesn't list is refused with the ones it does:
jadpo deliveries --state stuck error stuck isn't a state
- reason
- The states listed are
failed,outcome_unknown,diverged,unfinished,pending,running,held,dismissed,cancelledandabandoned. - next
- Use
--state pending, or leave it out (agent) - rule
- cli.
deliveries_ arguments - help
- https://jadpo.
dev/docs/errors/cli. deliveries_ arguments
How to fix it
If you meant to act on one, list them first, then name it by its id:
jadpo deliveriesjadpo deliveries retry <id>
The list shows each delivery's id, state and what went wrong.
Related
Markdown for agents: /docs/errors/cli.deliveries_arguments.md.Built from Jadpo main at aee2e8f.