Tooling · rule
deployable.settle_unrun
Route waits for follow-on work its deployable doesn't run.
Area 14, Tooling; not declinable; the next step is usually the agent's.
A route with settle: waits for the subscribers of what its action
emits, so the deployable that serves it runs them. The notes board waits
for each note to be pinned up:
use board/types { NewNote, NoteView }use board/actions { add_note }use board/queries { note_for }/// The notes board.routes Notes { prefix: /notes /// Adds a note, once it is pinned up. POST / { authentication: RouteAuthentication.none input: NewNote output: NoteView status: SuccessStatus.created run: add_note(input) settle: { answer: note_for(result.id) within: 2s } }}
and the kiosk serves it, while the worker runs the subscribers:
application { deployables: { kiosk: { serves: [main] target: Target.native } worker: { runs: [Trigger.subscribers] target: Target.native } }}
error: `POST /notes` waits for follow-on work `kiosk` doesn't run --> app.jadpo:3:9 |3 | kiosk: { | ^^^^^ doesn't run subscribers reason: `POST /notes` in `main` has `settle:`, so it waits for the subscribers of what its action emits, and a deployable runs them only when its `runs:` lists `Trigger.subscribers`. next: Add `Trigger.subscribers` to `kiosk`'s `runs:` (agent) rule: deployable.settle_unrun help: https://jadpo.dev/docs/errors/deployable.settle_unruncheck failed: 1 error, 11 files
Markdown for agents: /docs/errors/deployable.settle_unrun.md.Built from Jadpo main at a707efb.