#[non_exhaustive]pub struct CronReceipt {
pub job_id: Option<String>,
pub next_fire_at_ms: Option<i64>,
pub jobs: Option<Vec<CronReceiptJob>>,
}Expand description
Cron’s details payload.
Every field a family owns lives here, under the container’s one details
key, rather than flat beside the discriminators — the governing rules as
amended. Each is a bounded machine fact: scalars, short identifiers and
a small fixed-shape array of those.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.job_id: Option<String>Cron create and delete: the job id. On delete’s missing arm this
is the caller’s own id echoed back under the governing rules declared
echo — that arm has no server-side subject to name.
Also the field governing rules declaration names as conveying the hidden
fact on the declared created + cancelled pairing: a job row was
committed and will fire.
next_fire_at_ms: Option<i64>Cron create (created, duplicate): absolute epoch-milliseconds of
the job’s next scheduled fire.
jobs: Option<Vec<CronReceiptJob>>Cron list: the served jobs in server order, active and firing
rows only.