Thanks for letting me know!

This is fixed now, I'll look into why the monitoring tools didn't catch this one as they should have.