Hello, we are using Umbraco Cloud with Umbraco v13 and the default External examine indexer. We have 8 different node types we are filtering on the search of the site. At some point on our Live site, Examine(the external index) stopped indexing everything and was only returning data from 1 node type. Those nodes are only updated by a Hangfire recurring Jobs. It worth to mention that our staging site, which have the same recurring jobs and almost the same data from the Live site, it is working perfectly fine, the Examine external index is returning all the expected results. Hence, after reading a bit, we decided to push the "red" Rebuild index button. After that, more content was coming up, but not all of them. Only the recently published one, like the ones updated by the Recurring jobs. And a couple of other that were "Save and Published" after the rebuild. The rest of the nodes that were published before the rebuild are not showing up. Does this rings a bell? Is there a way to force an import of the old published content? FWIW, the internal index returns all the expected data. And no errors were found on the logs related with Examine or "ExternalIndex". Als, the rebuild on the Umbraco interface was finished after about 2 minutes but on the logs you can see it took more than 20 minutes https://cdn.discordapp.com/attachments/1296843811300970579/1296843811728916500/Screenshot_2024-10-18_at_11.33.26.png?ex=6713c36a&is=671271ea&hm=0313e1fa3de36a83cdee8d2240c86a6f4311a7e8561b59ed4606a662b909e4af&

Did you check the content after the interface was done or after the "Rebuilding index ExternalIndex done" message was shown in the logging? The interface starts a background task, hence why the interface is done in 2 minutes but the actual indexing takes around 20 minutes

Hello @Patrick de Mooij , Thanks for replying. Yes, I checked the content. and in deed the problem persists. If I "Save and Publish" an already published node, it gets indexed. Right now, as a workaround, I'm creating a command to iterate over all the Published Contents and trigger a "Save and Publish" to include them in the External Index. I'm pretty sure there is something wonky with the Examine External Index, but there is not clue of it in the logs.