Audit log should track actions taken, not actions attempted
Pitch
I think it would make more sense for the audit log to reflect actual actions and changes in state. Idempotent calls should not generate an audit log entry. Failed calls should not generate an audit log entry.
Motivation

Looking at this audit log, you can see that the order of events makes no sense, and this is because all actions were performed by manual API calls rather than through the web interface. Given that it is possible to make such API calls in any order, it is therefore also possible for the audit log to be confusingly ordered.
Another can of worms -- methods such as updating a DomainBlock or IpBlock with a comment that is exactly the same as the existing comment will still generate an audit log entry