> I don't see the value in having 2 different code paths here. Especially as the response in both situations is basically the same: "We're not sure what happened, but it could be a KahaDB issue. Check the docs plz".

Okay - I can fix that up.

> Also, I'd move this catch and the resulting error message to the caller...the mq namespace should strive to be PuppetDB-neutral.

I had this originally, and I was asked to move the logic here in a previous review.