Why do flows stop receiving message un-notified?
Jordi Unconfirmed, Member Posts: 10 ✭
we implemented a Solace consumer using the .NET API following the guidelines (https://tutorials.solace.dev/dotnet/persistence-with-queues/).
We use one session for several flows on distinct queues, respectively.
Sometimes, one of these flows stops receiving messages even though there are still messages in the queue, whereas the other flows are still getting messages.
Restarting the session/flow fixes this, but the problem is that we do not get an exception/error or notification that the flow stopped or went asleep somehow. Are there any intrinsic timeouts we are not aware of or what might be the problem here?