Piperack doesn't reset error messages?

[ndw]

From email:

I know this is probably not high on your priority list, but I’m having troubles using piperack.

What happens is that I have a pipeline that (for test purposes deliberately) ends in an error (piperack returns an http status 500). Fine.

What I see happening is that the error message from previous runs stays there and the new one is appended to it, even though I dutifully do a /reset action on the pipeline before I run it. This leads to getting longer and longer error messages.

Did you maybe forget to reset the error message (buffer) when somebody does a /reset? It looks that way.
I’m not sure whether you still do these kinds of maintenance things. If so, I would be very grateful.