I work in a very similar format, although I'm used to a fourth environment @2 - QA (quality assurance), to test any release pre user acceptance (third party software). Even still there are aspects that are unique across environments which cannot be fully tested by any release process e.g. more than likely (hopeful at least) prod will be on a different server and that may then involve complications specific to that environment! However this issue does suggest one of two things (or a combination) - shared server and some references have been broken, or a lot of test/defunct data has piggy backed the release. As long as it gets fixed we're all okay... disappointing, but communication is pretty good to be honest: much love @bnghelp0!!