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.

Area 14, Tools; not declinable; the next step is usually the human's.

Why Jadpo refuses it

Each schedule keeps its next due time and its lease, the claim that lets one run happen at a time, in a table of the database that keeps the schedules' state, and each run's record in another. jadpo schedules and jadpo why read them there, and pause, resume and run change them. The tables come with the migration that adds the first schedule. When the database can't be reached, or has no such table, there is nothing to show or change, so the command stops before it does either.

Jadpo won't apply the migrations for you here or try another address. The database may be production's, and whether it is the right one only you know.

What it looks like

A project with one schedule:

domains/planning/schedules/tidy_up.jadpo:

use planning/actions { tidy }/// Tidies up every quarter of an hour.schedule tidy_up {    every: 15m    run: tidy()}

jadpo schedules against a new database, to which the project's migrations haven't been applied:

jadpo schedules

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides which database the command reads, and whether its schema changes.

A database whose server isn't running gives the same error, saying it can't be reached. Here DATABASE_URL, the variable the connection's setting reads, names a database on this machine with no server running:

DATABASE_URL=postgresql://localhost:5499/app jadpo schedules

How to fix it

The question is whether the address names this project's database.

If it is this project's database, not yet migrated, apply the migrations, then run the command again:

jadpo migrate applyjadpo schedules

The tables are made, and the command reads them.

If its server isn't running, start the server, then run the command again:

jadpo schedules

The command reaches the database and reads it.

If the address names another database than the one you meant, such as production's, name that one with --url:

jadpo schedules --url "$PRODUCTION_DATABASE_URL"

The command reads that database instead, and leaves the other alone.

Related

• jadpo schedules
• Watching schedules
• Where a schedule's state is kept
• jadpo migrate