That does sound like a reasonable idea.BigBlockMopar wrote:Just shooting an idea here; Maybe incorporate a log-rule that prevents writing to the log, if the newest message is the same as the last one (except for the timestamp).
And perhaps then occassionally show a log-entry that the last error message occured n-number of times in a period of x-seconds.
While I'm not sure what action triggered the repeated error, it is not hard for an error to happen in a loop. Global protection would good.