Latest production update unexpectedly caused the issue, as soon as it was identified as the source it was reverted to restore functionality
Currently being investigated