It is likely that a fast "spike" of data, caused by a sensor or electrical glitch, is to blame. The best way to answer the question is to dump the data as a time history, and look for the exceedance as a spike that is not consistent with the rest of the data. For example, the torque jumps up in a fraction of a second, but the collective pitch does not, and the altitude and load factor doesn't change. This quick study is proof positive that no actual exceedance took place, and the only maintenance action would be to solve the erratic reading.
I had such an occurrence back 30 years ago in an S-61, where the Time-Temp recorder (a new installation of the type) flagged a massive engine overtemp, and the "exceedance police" came to cut off my head. It turned out that a voltage glitch on shutdown created a mythical temp spike that was flagged.