Nak does not immediately lead to a message redelivery

[funkye]

Greetings. I found some strange problem with Nak.
In some cases in our product, Nak does not immediately lead to a message redelivery. Instead, the message is sent again after the accept timeout.
However, I do not have any error when calling the Nak client method in problematic cases. The internal fields of the 'msg' class become the same as in the case of successful execution of Nak.

I also cannot reproduce the problem separately from the product and cannot understand what additional actions lead to this behavior.

I didn't find similar problems on the forum. Maybe you have encountered something similar or can you advise how to debug what is happening on the server at the moment? I read about enabling tracing on the server, can this help with debugging and maybe I should pay attention to some specific messages?

Server version: 2.10.14
C# Client library version: 1.0.4