Capabilities
Scheduling & Time
Durable delayed commands and recurring jobs that survive restarts and never double-fire across a cluster.
“Send the reminder 24 hours before the event” and “close the books nightly at 2 a.m.” both sound trivial until the box running the cron job dies silently, or six redundant servers all run the payout at once.
What ships: durable delayed/deferred command delivery (schedule a
command now, execute it later — through the same pipeline as everything else),
background jobs and recurring cron schedules via IRecurringScheduler with
cluster-safe single execution, and consumer second-level redelivery for
transport-level retry with backoff.
The stories behind it: The Reminder That Arrived a Day Late and The Nightly Job That Quietly Stopped.
Learn by building
The tutorials for this area, in order — each with a runnable sample.
018SchedulingSome work shouldn't happen now — it should happen later: send a reminder in 30 minutes, expire an unpaid order in an hour, retry a failed call after a backoff.
019Recurring JobsArticle 018 scheduled one-shot future work. This article covers the recurring case — "every night at 2am," "every Monday," "every 15 minutes" — and the job as the unit of recurring/background work.