Skip to content

Questions? Join our Discord.

JasperFx

Formal support for Wolverine, Marten, and Polecat is available through our Support Plans.

Recurring cron schedules: a message on a cadence, once per cluster Added 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, when a schedule that fires every few seconds or minutes arrives late, or when an agent must list, pause, resume or trigger one. Covers the four registration overloads, why the schedule name is an identity, the two execution paths since Wolverine 6.52 (the scheduled-message path and one timer agent per short-cadence schedule, TimerThreshold, UseTimer / UseScheduledMessages), what pause, resume and trigger do on each path, cluster semantics and the failover double-fire window, why resuming never backfills, the console's freshness, executionPath and owningNodeNumber fields, and reading a refused action back with get_command_outcome (CritterWatch 1.2).

Skill details ​

  • Skill name: wolverine-messaging-recurring-schedules
  • Applies to: wolverine
  • Tags: wolverine, messaging, scheduling, cron, recurring, background-jobs, clustering, timer-agents, critterwatch, mcp, agents, get_command_outcome
  • Added in: 1.14.0
  • License: Proprietary. Copyright JasperFx Software LLC.

Proprietary. Copyright © JasperFx Software LLC. See the license for terms.