Scheduled messages: one message, later New in 1.14.0
One-off delayed or at-a-time messages in Wolverine outside a saga: DelayedFor / ScheduledAt return values, OutgoingMessages.Delay / Schedule, bus.ScheduleAsync and DeliveryOptions.ScheduledTime / ScheduleDelay. Covers why a scheduled message is a publish (no route means it silently goes nowhere), where the schedule actually lives per destination (broker-native, message store, or process memory), the default local queue that holds schedules IN MEMORY even when a message store is configured (AlwaysMakeScheduledMessagesDurable / UseDurableLocalQueues), polling precision, cancelling and rescheduling through IScheduledMessages and what it cannot see, and designing the handler to check on arrival rather than relying on cancellation.
Use when a message should run later, when a scheduled message was lost on restart, never fired, or fired late, or when choosing between a scheduled message, a saga timeout and a recurring schedule.
Skill details
- Skill name:
wolverine-messaging-scheduled-messages - Applies to:
wolverine - Tags:
wolverine,messaging,scheduling,delayed-messages,durability,outbox,cascading-messages,local-queues - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.
This skill is part of a paid product. The full content of wolverine-messaging-scheduled-messages (patterns, code examples, conventions, and guidance) is distributed only to licensed customers.