-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any option to have Fault<> consumer in MassTransitStateMachine? #54
Comments
Yes, Faults can be observed by state machines.
To initialize it:
Correlating on the original message property, which is included in the fault message. |
@phatboyg |
If a consumer throws an exception, and exhausts all retries, the Fault is published by MT. Assuming that a saga is observing that Fault event, and it can be correlated to a saga instance, either a new instance or existing instance, it would be delivered to the saga. |
Thanks, you’ve helped me a lot |
I have a saga which subscribes to response events which are produced by external services. In other words, saga publishes message, external event handler subscribed and responds to saga. These external event handlers have also Fault<> consumers. So, the question is, can saga be configured subscribe to these fault consumers ?
The text was updated successfully, but these errors were encountered: