deliveries.unavailable

The app's deliveries 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

jadpo deliveries lists and acts on the app's event deliveries and schedule runs, which Jadpo keeps in tables of their own in the app's database. Those tables come with the project's migrations. When the database can't be reached, or has no such table, there is nothing to list or act on, so the command stops before it reads or changes anything.

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 where adding a note emits NoteAdded, which the subscriber share_added delivers:

domains/notes/subscribers/share_added.jadpo:

use notes/actions { share_note }use notes/events { NoteAdded }/// Shares each note once it is written down.subscriber share_added {    on: NoteAdded    run: share_note(event.note_id)}

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

jadpo deliveries

(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 deliveries

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 deliveries

The tables are made, and the command reads them.

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

jadpo deliveries

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 deliveries --url "$PRODUCTION_DATABASE_URL"

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

Related

• jadpo deliveries
• What an operator sees
• jadpo migrate
• Database and other connection URLs