I’ve been thinking about this one … I guess if there are multiple types indexed at the time, then it would be helpful to record the first N failures for a type; otherwise, we could end up telling the user just about one type while the remaining ones also have problems? In other words - have a limit of messages per BatchIndexingWorkspace.