Hi @tw2113, thanks for following up. I ran it a couple of times via CLI, and it kept on quitting at 78%; it would not return any errors, which added to the confusion.
So I then proceeded to run it with a –from_batch=, it also kept on quitting on a specific batch number for some reason. I tried running it with verbose to try to get more information on the run, but I think this isn’t supported yet, as it returned Error: Parameter errors: unknown –verbose parameter
I eventually got the reindex to resume by incrementing the batch number; it resumed from that point until it completed at 100%.
I just do not know what was wrong with that specific batch number.
So to sum up, resolved, but have no clue why that specific batch number interrupted the reindex. Adding support for verbose or anything that can provide more specific information would be helpful when troubleshooting these types of issues.
If anyone else encounters this problem in CLI, take note of the last batch run before the interruption and run:
wp algolia reindex –all –from_batch=xxx (last batch number)
