# `cli.why_arguments`

A `jadpo why` command names no schedule, one the project doesn't declare, or more than one.

Area 14, [Tools](/docs/tooling.md); not declinable; the next step is usually the agent's.

## Why Jadpo refuses it

`jadpo why` says why one schedule didn't run, or how its last run went. It explains one, by its name, and a name it doesn't know could be a typo for another.

## What it looks like

A project with no schedules:


```sh
jadpo why nightly_digest
```

```text
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.why_arguments
  help: https://jadpo.dev/docs/errors/cli.why_arguments
```

`(agent)` at the end of the `next:` line means your coding agent can make the fix itself.

## How to fix it

**If you meant a schedule the project declares**, name it as its declaration does:

```sh
jadpo schedules
jadpo why <schedule>
```

`jadpo schedules` lists each schedule's name.

## Related

- [Commands for debugging, editors and help](/docs/commands-for-debugging-editors-and-help.md)
- [Watching schedules](/docs/what-an-operator-sees.md#watching-schedules)