Build complete job and calendar blocks from a form. Copy-paste straight into your Croniqfile — no Croniq install required.
Disabled jobs stay in the Croniqfile but never fire. Useful during incident triage when you want the config in source control but don't want triggers to enqueue.
Shares one budget with every other job naming the same group.
Needs a matching concurrency_group <name> { max_concurrent N }
block in your Croniqfile — an undefined name is a config error.
priority — when a backlog drains, waiting
executions of higher-priority jobs are dispatched first. Each
five minutes of waiting counts as one level up, so nothing
waits forever.
coalesce — a trigger that carries no
payload folds into an execution of this job that is already
queued, so twenty events in a minute produce one run rather
than twenty. A trigger carrying metadata always gets its own
run. Not available on ephemeral jobs.
coalesce schedule — for a poller that
drains whatever is open: a scheduled fire that falls due
while a run of this job is still queued folds into it
instead of queueing another, so after a stall one run waits,
not one per missed minute. Includes the trigger fold above.
run_on_register — also fires the job when croniq
first sees it and whenever its definition changes, for work
that has to happen at deploy time and not only on schedule.
Not on every restart or reload.
Green = an include rule covers this day.
Red = an exclude rule wins.
Empty = no rule activates the day.
The grid is a static preview; the Croniq scheduler also
respects timezone, time-of-day windows, and rule ordering.
These are top-level blocks — paste them at the root of your
Croniqfile, outside any job. Secrets
(SMTP password, tokens) are intentionally not part of the DSL;
supply them via environment placeholders like
{env.NAME}.