I am unable to see the error count in container tab even though the error occurred during the test, the results come only for passed transactions.
I think I have faced the same issue if I understand you correctly.
How have you defined your error handling in the Runtime settings?
Is it "Go to the next iteration"? Because it seems that NeoLoad is not really behaving logically when this happens. It aborts the container without showing the exact error. It also skips the pacing when this setting is used.
I've done some small tests and came to the following set-up:
1. On virtual user level both error occurs & assertion fails are set to do nothing
2. In the action I have specified the pacing
3. In the action I immediately have a Try-catch. The try-part contains the whole script that needs to be executed.
The catch part is empty. If you put the "Go to next iteration" it seems to skip the pacing defined in the action again. In my case this is unwanted.
There is still something that I find unwanted:
I have a GWT-application and my script has containers (=user actions). In the containers there are Web pages and in the web pages there are multiple requests. With the set-up as describes above if an error occurs in one of the requests, then the Web page also fails (=correct behaviour) and the container fails (=correct behaviour). But requests in the same Web page, but after the failed request, are still executed (=unwanted). So in the attached screenshot 'Request 2.2' fails, but Request 2.3 & 2.4 are still executed.
I hope this answers your question.