@blackTshirt Maybe you don't have the right permissions to view the error under the role you are logged in? Do you have another role that has the right permission to view the error?