We have 3 clients now reporting a search limitation for large result sets. It seems there is a roughly 15 second timeout for search results, preventing very large searches from being possible in Workflow or manually.

The 3 enivornments with this problem are trying to store and search large amounts of data. If they can limit their results to be in the 10's of thousands there should never be a problem, but for the larger searches, the timeout is reached and they receive a 9008 error translating to a SQL timeout error in the event log.

The exact limitation might be dependent on hardware technology where the SQL server resides, although it is unclear which hardware allows for different limitations in search results.

I think rather than canceling the search, the timeout should allow for larger searches. I wonder if a timeout should be included at all, nothing wrong with waiting 5 minutes to get a large result set back.