When using a Browser Driven Load Testing (BDLT) approach with 'TrueLog on Error' enabled, only the last API call which produces an error has a rendered image in the generated TrueLog (assuming a rendered Web page is available for a screenshot to be taken).
This is as designed as it is too resource intensive to keep more screenshots available in memory until an error occurs.