ClientSubscriptiononError() reports the error EnumStatusCode_BadSequenceNumberInvalid. What is the reason for this error and how to solve it
This article is relevant for all .Net products
This error occurs when a publish notification is missing or one publish notification overtook a previous notification. This can happen on networks, for example when packages are sent over different network routes or when a packet is completely lost. For such situations the SDK provides an automatic republishing feature, which can be enabled by Client::Subscription::setRePublishingEnabled(). The republishing service which requests the server to resend the missing publish responses and the SDK then ensures to report the publish responses to the API in the correct order. If an application is only interested in the newest notifications, then the error EnumStatusCode_BadSequenceNumberInvalid can simply be ignored.