Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 30 Oct 2026. What's built · Install 0.1.0
jadpo
Reference: Jobs and events

Jobs and events · rule

schedule.item_invalid

Schedule holds an item it doesn't take, gives one twice or leaves out every: or run:.

Area 12, Jobs and events; not declinable; the next step is usually the agent's.

A schedule holds every: and run:, once each; how it is retried is the same for every schedule:

example
action tidy() -> Unit {}/// Tidies up every quarter of an hour.schedule tidy_up {    every: 15m    run: tidy()    retry: next_schedule}
text
error: `retry` isn't something a schedule holds --> main.jadpo:7:5  |7 |     retry: next_schedule  |     ^^^^^ not a schedule item  reason: A schedule says how often it runs with `every:` and the action it runs with `run:`; nothing else, since one run at a time, merged missed ticks and the next tick as the retry are how every schedule runs.  next: Write `every: <duration>` and `run: <action>()`, once each (agent)  rule: schedule.item_invalid  help: https://jadpo.dev/docs/errors/schedule.item_invalidcheck failed: 1 error, 1 file

Markdown for agents: /docs/errors/schedule.item_invalid.md.Built from Jadpo main at a707efb.