status endpoint breaks if circular reference is introduced into object

[EvaLok]

while this should be fairly rare, it's certainly unexpected behaviour, and as the only reason we want the object is for reporting purposes, we should simply clone message objects instead of saving a reference to them

[EvaLok]

fixed