{"section":"known-issues","requestedLocale":"en","requestedSlug":"search-api-returns-timeout-when-querying-large-master-data-entities-without-filters","locale":"en","slug":"search-api-returns-timeout-when-querying-large-master-data-entities-without-filters","path":"docs/en/known-issues/Storage/search-api-returns-timeout-when-querying-large-master-data-entities-without-filters.md","branch":"main","content":"## Summary\n\n\nMaster Data Search API requests may experience timeouts when querying Data Entities containing a massive volume of documents (e.g., tens or hundreds of millions). This occurs because the search operation defaults to calculating the exact total number of matching records. On extremely large datasets, this calculation requires a full scan that exceeds the API's timeout limit.\n\n#### Simulation\n\n\n\n1. Identify a Master Data Entity with a very high volume of documents (e.g., > 50 million).\n2. Perform a generic `GET` search request to the Search API without applying specific or indexed filters.\n3. Note that the request takes a long time to process and eventually fails with a Timeout error (408 Request Timeout).\n\n\n#### Workaround\n\n\nTo mitigate this issue, ensure that search queries include specific filters—preferably on indexed fields—to reduce the scope of the database scan. Avoid broad, unfiltered searches on large entities."}