When the MassIndexer component detects an exception during loading of primary keys, it correctly reports the Exception to the ErrorHandler and aborts the indexing job.

The two actions are however handled by different components, and there is a missing guarantee that the ErrorHandler will have had a chance to actually fire before the indexing job is terminated.

This might lead to jobs being terminated (correctly) but the state of the job isn't yet marked as failed, so checking the state right after the MassIndexer terminated might (wrongly) report that it's done without any error.