Hola Katherine,
I am surprised to hear that using the "Include descendants" option did not successfully update the publication status of the child descriptions!
Do you get any error messages when re-indexing?
How much memory does your installation have? I have only found one other thread in the user forum with the same error message and it's from 2010 - but the issue then had to do with a lack of available RAM. If you want to investigate whether or not Elasticsearch is part of the problem, this thread has a lot of tips and links:
However,
first I suggest that in addition to clearing the application cache (
php symfony cc), you also try
restarting PHP-FPM. Additionally, please try testing in an incognito / private browser window, or else clear your web browser cache first - I want to make sure that we are seeing an updated version of the page and not a cached copy.
You could also try checking for data corruption - if some part of your import timed out before completing, it's possible that some key rows in the import were not populated, leading to errors. We have a SQL query in the Troubleshooting documentation that can check for (and fix) the most common forms of data corruption, here:
For general instructions on how to access the MySQL command prompt, see:
In the meantime, I will ask our developers if they have any further ideas.