Improve error handling during audit trailing WIP

I eventually keep the `exception` in our private case for legacy reason, but the more I think about it the less I think we need it. Yet, some may argues that we catch the least possible exception and so we need to record the traceback too.

In this case, it is a very lazy usage of a "catch-all". The main issue here is that it raises something, catch-it and continue like nothing happened.

So, error or exception, there is no perfect choice - albeit the original message is better, thus should be kept.