An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
Hi @Vishakha Bansal
When indexing a very large number of files from Azure Blob Storage using Azure AI Search with a skillset for chunking and embedding generation, it is common for indexer runs to partially process documents or fail after long execution times. This typically happens because AI enrichment pipelines are resource-intensive and can encounter service throttling, long processing durations, or temporary authentication issues with the storage account during extended runs. For large datasets such as thousands of files, it is recommended to run the indexer on a schedule rather than relying on a single long execution. Scheduled runs allow the indexer to continue processing remaining documents and automatically retry transient failures. It is also important to ensure the search service has sufficient capacity (replicas or partitions) to handle enrichment workloads, and to monitor the indexer execution history so that failed items can be retried. These approaches help ensure that all documents are eventually indexed and reduce intermittent authentication or partial-run issues during large-scale indexing.
https://learn.microsoft.com/en-us/azure/search/search-indexer-troubleshooting
https://learn.microsoft.com/en-us/azure/search/cognitive-search-common-errors-warnings
Let me know if you have any further assistances needed.