We have an integration that builds a search request into our NetSuite environment looking for item fulfillments to send to our Shopify store. The search is overall pretty straight forward where we are looking for item fulfillments in the shipped status, in a particular location, for a particular customer, hasn't been modified in the last 2 minutes, and finally a custom string that tracks the status of the item fulfillment. After the integration works with the item fulfillment, it will update the status accordingly so that it falls off the next search request.
This integration works great all day everyday, but we recently attempted to reprocess a few fulfillments by setting the custom string so that it would be picked up by the integration. It reliably fails due to the web service call timing out after nearly 7 minutes. After we take the item fulfillment back out of the search response, the integration works fine.
Webservice Version: SuiteTalk SOAP Web Services v2018_1
Error code: SEARCH_TIMED_OUT
Message: Your search has timed out. If your search includes the 'contains' operator, try using 'hasKeywords' instead. If your search includes broad search criteria, try narrowing the criteria.
While we understand that a search request with a wide berth would likely timeout, we just aren't sure why setting the custom field to another value in the UI would cause the request to timeout.
Any insight would be helpful and greatly appreciated as we are very confused why this would be happening.