From user:
I just noticed that a build can fail in several different ways. A normal failure like a compilation error or something simple causes QB to stop building and send out notification to those registered. Everything is good with that type of failure. However, another type of failure is when something more serious fails causing the build configuration itself to fail. This is where you get a red square for both the specific build that failed plus a red square for the configuration log. When this happens, the whole build stops and nothing happens. No build notifications and no other steps are run afterwards that had a build necessary condition of true (these should run regardless of anything else).

How do I get my build necessary "true" steps to run all the time? Why does a configuration error cause the whole build to stop and not send email notifications?

My pariticular example is that my master QB server does a checkout of a child QB server. The compilation on the child fails causing its artifacts not to be created and published. The master server gets a:

java.lang.RuntimeException: Failed to batch download from QuickBuild repository "http://bail.lgc.com:8080/app.do".

with an HTTP 500 response code because it can't find the artifacts from the child to download.

This "failure to batch download" error should be considered a normal error and not stop the whole thing so that build notifications and other build necessary "true" steps can still run as they are supposed to.