Recurring cron schedules: a message on a cadence, once per cluster New in 1.14.0
Cron-scheduled recurring messages in Wolverine 6.34+ (opts.Schedules.ScheduleRecurring) and how to operate them from CritterWatch.
Use when a job must run on a cadence, when choosing between a recurring schedule and a one-shot scheduled message or a self-rescheduling handler, when a schedule fires twice or not at all in a cluster, or when an agent must list, pause or resume one. Covers the four registration overloads, why the schedule NAME is an identity, the two durability flags registration flips and the table it provisions, single-agent cluster semantics and the failover double-fire window, main-database-only scope, why resuming never backfills, and the freshness rule for the console's paused / nextOccurrence fields.
Skill details
- Skill name:
wolverine-messaging-recurring-schedules - Applies to:
wolverine - Tags:
wolverine,messaging,scheduling,cron,recurring,background-jobs,clustering,critterwatch,mcp,agents - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.