The current behavior is that the receipt modAck is "fire and forget", much like non-EOD receipt modAcks.
However, any delivery to the client logic should block on a successful receipt modAck. If the receipt modAck fails with a permanent error, we should not send the message to the client and not even log it. If it's a temporary failure, it should be retried.
The current behavior is that the receipt modAck is "fire and forget", much like non-EOD receipt modAcks.
However, any delivery to the client logic should block on a successful receipt modAck. If the receipt modAck fails with a permanent error, we should not send the message to the client and not even log it. If it's a temporary failure, it should be retried.