-
Notifications
You must be signed in to change notification settings - Fork 70
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
Reusing Saga Coordinator #52
Comments
Since the saga has been marked as rejected, you cannot call it anymore. Otherwise you could end up with inconsistent state. What exact behavior would you expect? |
When once rejected state has occurred,in new order created request saga flow not working properly. Example ,first order request comes Handle(OrderCreated @event) calls related OrderCreated Handle then calls ProductReserved Handle method, in example scenario when product reserved occurs an error so ReserveProductRejected Handle is called. Reject(); calls it's CompensateAsync(ReserveProductRejected method then other compansate method. Untill now its every thing is ok but if there is another order request comes with same scenario only OrderCreated handler called by saga coordinator.ReserveProductRejected handle method not calling. public class ApproveOrderHandler :
} public class ApproveOrderSaga : Saga,
... |
How do I reuse the coordinator. I tried to use the Reject functionality and it's working fine. But the next time unable to use the coordinator in subsequent request. I can see the state as Rejected.
The text was updated successfully, but these errors were encountered: