The bulk re-index button at the top of the “Search page” settings, the one that dictates whether or not to replace WordPress’ with Algolia, whether just on the back end, or also with Instantsearch, should help handle getting back catalog indexed as well.
Technically a cron job could as well, but there’s other potential concerns there.
https://github.com/WebDevStudios/wp-search-with-algolia/issues/10
If you’re able to make use of WP-CLI, the plugin does have wp algolia re-index
command, that you could set up a recurring schedule to run.
If you don’t have WP-CLI, then I technically outlined a way to add your own code to do the same, seen at https://github.com/WebDevStudios/wp-search-with-algolia/issues/10#issuecomment-1275507679
HOWEVER before you go running off to implement I want to point out my followup comment from last month over at https://github.com/WebDevStudios/wp-search-with-algolia/issues/10#issuecomment-1430613581
If I was to try and do a cron setup, I’d likely go with the authenticated WP-CLI version if absolutely needed, otherwise the index should be self regulating with new content and automatically pushing up upon publish, and the bulk re-index would cover existing content.