Found it. A third party contractor had disabled the script deployment without us asking them to. That's disconcerting...