Reputation: 1
I have vs 2015, NServiceBus 4.6.0.0, RavenDb 2.5.
I deployed a new release of my software and 1 saga is experiencing saga not found errors on at least two messages associated with the saga. When we rollback the release the messages are reprocessed without error.
I have used some c# code to access the saga data and that works fine. There are 600+ sagas in our production RavenDb. So I believe that rules out RavenDb as the problem and eliminates any changes to the saga object tree contributing to this issue.
so it looks like we are back at NServiceBus. I am at loss of what would cause these saga not found errors.
Any help would be greatly appreciated.
Upvotes: 0
Views: 371