I'm getting an "Recursive rendering detected when rendering entity" error while building my search indexes from drush.
I'm using nested entity references and presumably running up against the RECURSIVE_RENDER_LIMIT mentioned in #2803881: EntityReferenceEntityFormatter's RECURSIVE_RENDER_LIMIT producing lots of log messages → and #2828364: Default media stopped to render due to recursion protection being to protective → . Many nodes in a given index run might contain the same great-grandparent node, which needs to be indexed with its grandchild.
Any ideas on getting around this? Can it be safely ignored (and if so, is the content getting indexed)? If the content isn't indexed, why is Search API reporting that it is indexed?
Active
1.23
General code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is indeed related to the issue @heddn added but a quick workaround which doesn't need any patching is to lower the batch size. For me it worked if I lowered from 50 to 20 (This is the recursive limit set by core). Take into account this is not a fix but it seems the linked issue on core could have other impact.