Wolverine Sagas Added in 1.10.0

Stateful workflows with Wolverine sagas — Saga types, the Start/Handle/NotFound method conventions, how Wolverine resolves which saga a message belongs to (member conventions, [SagaIdentity], strong-typed ids, the SagaId envelope header), TimeoutMessage and why it is not a scheduled message, MarkCompleted, saga storage per persistence provider, two sagas on one message, and starting a saga from HTTP or gRPC.

Use when building a long-running workflow, migrating an NServiceBus or MassTransit saga, or debugging IndeterminateSagaStateIdException ('Could not determine a saga id'), UnknownSagaException, InvalidSagaException ('No known Saga persistence provider'), SagaConcurrencyException, or 'You must define the saga id when using the lightweight saga storage'.

Skill details

• Skill name: wolverine-handlers-sagas
• Applies to: wolverine
• Tags: wolverine, sagas, workflow, state-machine, timeouts, persistence, handlers
• Added in: 1.10.0
• License: Proprietary. Copyright JasperFx Software LLC.

This skill is part of a paid product. The full content of wolverine-handlers-sagas (patterns, code examples, conventions, and guidance) is distributed only to licensed customers.

Buy AI Skills