Expose root failure cause without having to "enable debug logging"

When EAS build fails for one reason or another, I very often end up with this generic error:

To see what actually is going on I have to rerun the job with "Enable debug logging" which feels unnecessary. It would be great if the root failure cause was exposed right away here.