When (re)indexing an item that can't be loaded a Could not load the following items on index %index: @items. warning is displayed. Besides that, the item is removed from the index & its tracker. The code responsible for this can be found here.
I'm working on a project that makes extensive use of external entities → . We're using Search API to index them to a Solr index, to make them searchable together with our local entities (e.g. nodes).
A few of these external entities come from API's that aren't always 100% reliable (e.g. they are experiencing issues, very short downtime, under too much load, ...). When this occurs at the exact same moment an external entity from one of these API's are (re)indexed, the external entity is removed from the index & tracker and they are no longer visible on our search pages.
If we have the option to disable the automatic removal from the index & tracker, we can circumvent these issues because a retry for these entities will happen on the next (for example) cron run.
Is there a chance we can make this configurable? I'm aware that there may be good reasons it works the way it does not, but I feel like this can be very handy for specific use cases (such as ours).
Active
1.0
General code
Oh boy - this is quite embarrassing :-)
I was looking at an older version of Search API. It appears this functionality has been added quite recently @ ✨ Do not delete items when loading fails Fixed .
Very awesome! Closing this one as this is obviously no longer needed. Sorry for the noise!