If the data in your index isn’t up-to-date, your indexing queue may be stuck. The queue relies on one of Magento’s indexers, added by the extension: the algolia_queue_runner.
Ensure the Magento indexer is “ready” by running the following in the command line:
php bin/magento indexer:status algolia_queue_runner
If the status of the queue is “processing” for a long time, it may need to be reset by running the following in the command line:
php bin/magento indexer:reset algolia_queue_runner
Monitoring the queue
From version 1.8 of the extension, there’s a monitoring page (at Stores > Algolia Search > Indexing Queue). This page contains a grid displaying the contents of the indexing queue. It lets you monitor the number of operations the queue needs to perform.
You can see details of each operation by clicking the ‘view’ link. Any error occurring during the job is logged in the Error Log attribute.
At the top of the page, the recommendations section helps you configure and optimize the queue in the best way possible.
If the indexing queue performs as expected, the number of jobs should decrease every 5 minutes (don’t forget to refresh the page). If the number of operations doesn’t decrease, ensure that the queue is correctly set up.
From version 1.8 of the extension, any failing operation that reached the maximum number of retries is archived in the algoliasearch_queue_archive table. This is another good place to check for error logs since the last encountered error is stored along with the job.