jadpo why

Explain why a schedule didn't run.

Answers why a schedule didn't run, or how its last run went (area 17), from its state and run records: it is paused, a run still holds its lease, a lost run held its lease past its expiry, ticks stopped arriving, or its last run failed, with the failure's code and kind. The answer comes first, then its facts, then the .jadpo place the schedule is declared in. Requests, events and records come with debugging (area 17).

jadpo why <name>

Arguments

• name: The schedule's name

Flags

• --url <url>: The database the schedules' state is in

On every command

• --json: Print data for tools instead of text
• --full: Show everything a report shortens
• --help: Show every flag, with examples
• --color <when>: Choose when to use colour

jadpo why --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("why"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.

Examples

# Find out why a schedule hasn't runjadpo why nightly_digest

Errors

• cli.why_arguments: A jadpo why command names no schedule, one the project doesn't declare, or more than one
• schedules.unavailable: The app's schedules couldn't be read from their database, because it can't be reached or has no table for them yet
• toolchain.project_not_found: You ran a command that works on a project in a folder with no app.jadpo, in it or in any folder above it