Exceptions after the first message are truncated in the logs, which can be a hindrance. Workaround right now is to call resetErrorCount() in strategic locations -- which works well if you know, roughly, where the exception is thrown.

This is a feature request from customer Leafy to add a flag to turn this off.