All HTTP 500 (internal server error) errors on production get captured by OCIO before returned to client and an OCIO issue page is returned with a HTTP 200 (everything is okay). That causes us to show screens like the attached.

Have JavaScript treat the OCIO problem screens the same way it currently treats HTTP 500 errors and write the OCIO issue information to the watchdog log. If the logging cannot happen we will not fix this issue because we need the issue number provided on the OCIO screen.