Waggle scheduler

Cron that works.

Leader-elected scheduling. Fires once per tick. Exponential backoff. 90-day audit log.

Waggle scheduling

Make the expression readable.

A cron expression becomes a readable set of firing times, with each illustrated dispatch recorded beside it.

Cron expression composer

*/15minute

*hour

*day

*month

*weekday

00····05····10····15····20····25····30····35····40····45····50····55····

Highlighted minutes match the schedule

Schedule definition

name = "refresh-index"
schedule = "*/15 * * * *"
timezone = "UTC"
target = "stinger://indexer"

At minutes 0, 15, 30, and 45.

Example execution

Dispatches0

Targetindexer

The controls demonstrate schedule interpretation. They do not create a scheduled job.

Job lifecycle

Define. Elect. Fire.

Define

Declare a cron expression with second-level granularity. Attach a target: a Stinger function, an HTTP endpoint, or a Buzz queue message. Waggle validates and persists the job.

Elect

Waggle nodes participate in leader election. Exactly one node owns the scheduler at any time. If the leader fails, a new leader is elected within seconds -- no gaps.

Fire

At the scheduled instant, the leader dispatches exactly once. If the target fails, exponential backoff retries up to a configurable maximum. Every attempt is logged.

Reliability

Every execution logged.

Trigger time, dispatch latency, target response, retry count, and final status. Query by job, time range, or outcome. Export via Taps webhooks.

1Execution per tick

90dAudit retention

<1sLeader failover

∞Schedules per org

Schedule your first job.

One cron expression. Leader-elected. Guaranteed single execution.

Start free →Read the docs

Waggle scheduler

Cron that works.

Leader-elected scheduling. Fires once per tick. Exponential backoff. 90-day audit log.

Waggle scheduling

Make the expression readable.

A cron expression becomes a readable set of firing times, with each illustrated dispatch recorded beside it.

Cron expression composer

*/15minute

*hour

*day

*month

*weekday

00····05····10····15····20····25····30····35····40····45····50····55····

Highlighted minutes match the schedule

Schedule definition

name = "refresh-index"
schedule = "*/15 * * * *"
timezone = "UTC"
target = "stinger://indexer"

At minutes 0, 15, 30, and 45.

Example execution

Dispatches0

Targetindexer

The controls demonstrate schedule interpretation. They do not create a scheduled job.

Job lifecycle

Define. Elect. Fire.

Define

Declare a cron expression with second-level granularity. Attach a target: a Stinger function, an HTTP endpoint, or a Buzz queue message. Waggle validates and persists the job.

Elect

Waggle nodes participate in leader election. Exactly one node owns the scheduler at any time. If the leader fails, a new leader is elected within seconds -- no gaps.

Fire

At the scheduled instant, the leader dispatches exactly once. If the target fails, exponential backoff retries up to a configurable maximum. Every attempt is logged.

Reliability

Every execution logged.

Trigger time, dispatch latency, target response, retry count, and final status. Query by job, time range, or outcome. Export via Taps webhooks.

1Execution per tick

90dAudit retention

<1sLeader failover

∞Schedules per org

Schedule your first job.

One cron expression. Leader-elected. Guaranteed single execution.

Start free →Read the docs