Skip to content

Comments

Support multiple saga types handling the same message type#2197

Merged
jeremydmiller merged 2 commits intomainfrom
sagas-respond-to-same-message
Feb 16, 2026
Merged

Support multiple saga types handling the same message type#2197
jeremydmiller merged 2 commits intomainfrom
sagas-respond-to-same-message

Conversation

@jeremydmiller
Copy link
Member

Summary

Closes #2195

  • When MultipleHandlerBehavior is set to Separated, multiple saga types can now respond to the same message type. Each saga gets its own independent SagaChain routed to a separate local queue, with independent lifecycle management (load, create, update, delete).
  • Throws a clear InvalidSagaException with guidance to use Separated mode when multiple sagas handle the same message without it enabled.
  • Added end-to-end integration test with Marten persistence verifying two sagas start from the same message and complete independently.
  • Added documentation section explaining the feature.

Test plan

  • CoreTests pass (1013/1013)
  • MartenTests saga tests pass (53/53, including 2 new tests)
  • New test multiple_sagas_for_same_message verifies:
    • Two sagas start independently from the same OrderPlaced message
    • Completing one saga does not affect the other
    • Each saga completes independently via its own message type

🤖 Generated with Claude Code

jeremydmiller and others added 2 commits February 16, 2026 09:41
When MultipleHandlerBehavior is set to Separated, Wolverine now allows
multiple saga types to respond to the same message type. Each saga gets
its own independent handler chain routed to a separate local queue.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support having multiple Saga type respond to the same message

1 participant