My personal takeaway, when it fails and you can't blame anyone for any reason, blame a tool.
You'll get the whole team helping you when replacing the tool and setting up a better solution.
If you blame anyone, people will start to be extra cautious and won't take any initiative.
But don't overuse it, if you always blame the tool, you'll end up like my ex colleague "Steve" where every failure was Microsoft's fault.
I've always been fond of blaming myself and asking everybody else to help make sure I don't cock it up a second time - when it works out I get lots of help, lots of useful feedback, and everybody else feels good about putting the effort in.
This does require management who won't punish you for recording it as your fault, though. I've been fairly lucky in that regard.
Your ex-colleague may not be factually correct, but I agree with him in spirit.
If you use powershell, what's your reaction when you delete some stuff by using the "-Force" parameter and that it's deleted ?
Steve usually said that Microsoft should ask for a confirmation before deleting anything, even with the "-Force" parameter.
It was Microsoft's fault when the whole test environment, that he spent two days setting up, was deleted with the "-Force" parameter. He said something along the lines of "Microsoft shouldn't let me do this".