Hi Eric and Thomas
It's a matter of timing.
In the application as it stands, the ResendLimit says the max times the relevant communication can be resent - if instances were to be resent now.
It is perfectly plausible for this to be set to say 5 initially, then someone decides it should really be 2 or 0 for whatever reason.
Future resends will adhere to the new limit, but old communications may have been sent more than the current limit.
Arguably, the limit and the count should both be on the individual log records, so we'd be comparing the limit to the count in force at the time the record was generated, but that is overkill (and besides, we may want it to conform to the current limit whilst the resends are happening).
If the value of ResendLimit - ResendCount is negative, this is telling us the communication was sent more times than the current limit, but is not an error as such.
I think I can live with a byte extra per row, cost is a fraction of a cent (or a second of my time).