Thanks for the heads-up; this is actually completely fixed because you can use the "async" automatic indexing synchronization strategy in order to index in the background, which will in particular log the indexing failures instead of throwing exceptions. And if that's not what you want, you can also define a custom strategy.

I'll mark this as fixed.