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.every_invalid

Schedule's every: isn't a whole number of seconds, minutes, hours or days.

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

every: is a whole number of seconds, minutes, hours or days:

example
action tidy() -> Unit {}/// Tidies up four times a second.schedule tidy_up {    every: 250ms    run: tidy()}
text
error: `every: 250ms` can't be how often a schedule runs --> main.jadpo:5:12  |5 |     every: 250ms  |            ^^^^^ not seconds, minutes, hours or days  reason: `every:` is a whole number of seconds, minutes, hours or days above zero (`30s`, `15m`, `1h`, `1d`), counted in UTC from when the application starts.  next: Write a duration such as `every: 15m` (agent)  rule: schedule.every_invalid  help: https://jadpo.dev/docs/errors/schedule.every_invalidcheck failed: 1 error, 1 file

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