-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unclear Error message, Unable to update saga with id #19
Comments
Noticed that one occurrence this happens is when multiple concurrent Saga Messages are being processed, would guess that Mongo fail to update the document due merge-conflicts. Maybe implementing a delta-update check would lower the risk, that is to store the original Data and only update the fields that have changed values. |
Having the same issue here. |
same |
What version are you running and could you provide a test that reproduces the issue? |
v2.0.3 |
Could be a clearer error message regarding why not be able to update Saga, in this case it seemed (not sure if the Saga was deleted) that there was no object with that ID.
Here is full call stack
The text was updated successfully, but these errors were encountered: