I mean ultimately the answer is that you have to put in a ticket with NS support, since only Oracle/NetSuite’s DBAs can really see what’s going on in the backend. That being said, exporting and sorting a search does cause it to completely re-run the search, so that’s something to note that even after the search has loaded once, if it took 20-30 seconds to run, it’s probably going to take at least another 20-30 seconds to sort it and another 20-30 seconds to export it as it completely re-runs each time you’re doing one of those activities. Another thing to note here is that you’re running a summary search, so you’re already probably pulling a lot more data than just what’s displayed in the search results, and then you also have sum() calculations in the formula, meaning that you’re asking it to run all that data again for for all the existing data for each line. So it is kind of a hard-working formula there, but it does seem weird that it would run okay normally, then bomb out completely when being sorted.  Usually when I run into things timing out completely, it’s because there’s a join to a table that’s custom and not well/correctly indexed, but that doesn’t look to be the case here as far as I can tell, although who knows. But yeah, I’d go ask support and just keep hounding them (it’s going to take a while and be a bit of a PITA) until you get to an actual DBA who’s pretty competent and hopefully they can pinpoint the issue.  Only other thing you could do in the meantime is to persist the search and see if you eventually get results (it’ll run for 2 hours asynchronously). If it bombs out there, support definitely needs to give you some sort of explanation as to why/where your search is getting hung up.