Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsTools · rule

deliveries.not_found

On this page

The id given to jadpo deliveries matches no delivery or schedule run in the database.

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

Why Jadpo refuses it

retry, dismiss, cancel, resolve, show and abandon act on one delivery or schedule run, named by the last 8 hex digits of its id, as jadpo deliveries lists it. When nothing in the database has an id ending that way, there is nothing to act on. The id may be mistyped, the item may be gone (a delivery every subscriber has had is deleted after 24 hours, and a schedule's run after 30 days), or the command may be reading another database than the one the id came from.

Jadpo won't act on the nearest id instead: retrying or dismissing the wrong delivery changes what the app does for someone.

What it looks like

A project where adding a note emits NoteAdded, which the subscriber share_added delivers:

domains/notes/subscribers/share_added.jadpo:

example
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 retry with an id that nothing in the database has:

shell
jadpo migrate applyjadpo deliveries retry 0a1b2c3d
output
Applied 1 migration to `main`    20261020T1400_initial  appliederror: No delivery or schedule run has the id `0a1b2c3d`  reason: `jadpo deliveries` lists those that need an operator, and `--state` the others; a delivery whose event every subscriber had is deleted after 24 hours, and a schedule's run after 30 days.  next: Run `jadpo deliveries` to see them, with their ids (human)  rule: deliveries.not_found  help: https://jadpo.dev/docs/errors/deliveries.not_found

(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 delivery is sent again.

How to fix it

The question is whether the command reads the database the id came from.

If it does, list what is there, with its ids, and use the id shown:

shell
jadpo deliveriesjadpo deliveries --state pending

jadpo deliveries lists what failed or is in doubt; --state lists the others, one state at a time.

If the id came from another database, name that one with --url:

shell
jadpo deliveries retry 0a1b2c3d --url "$PRODUCTION_DATABASE_URL"

The command finds the item in that database and acts on it there.

Markdown for agents: /docs/errors/deliveries.not_found.md.Built from Jadpo main at aee2e8f.