NetSuite saved search timing out at month-end? What to do

Why does it time out at month-end?

• The date range is at its widest. Oracle’s advice is to run searches “on a limited time range (smaller is always better).” A month-end search often covers the whole period, or the year to date.
• “Contains” is slow. Oracle calls the contains condition “one of the most resource-intensive search mechanisms.” Criteria such as “Memo contains accrual” or “Name contains” a customer group force NetSuite to read far more than it returns.
• System notes are heavy. Oracle advises avoiding system notes in searches “because they contain a lot of data.” Searches that show who changed what, and when, are often built on them.
• Everyone runs reports at once. Oracle says: “do not repeatedly attempt to run it during the time that the original report is still running. Executing multiple reports at the same time can cause significant performance issues.” Close week is when a whole team does exactly that.

How do you fix it yourself?

Work on a copy of the search, not the original your team relies on.

1. Run it in the background. Go to Reports > Saved Searches > All Saved Searches and click Persist (CSV) next to the search. NetSuite runs it in the background “for up to 3 hours” and saves the results as a CSV file, available for 7 days. Check progress at Reports > Scheduled Searches > Search Results, where the status reads Pending, Completed, Timeout or Failed. If you don’t see Persist (CSV), you need the Persist Search permission; ask your NetSuite administrator.
2. Shorten the date range. Run the period in weekly slices, or one subsidiary at a time, and combine the results. Smaller searches finish; one giant one may not.
3. Replace “contains”. Where every match begins with the value you’re looking for, use “starts with”. Where the value is a word inside the field, use “has keywords”. Oracle gives both as alternatives.
4. Drop system notes unless the report truly needs the change history.
5. Stop the re-runs. Nobody re-runs a search that is still running.
6. Schedule it. Scheduled saved search emails are set up on the Email subtab of the saved search. Oracle says scheduled searches run at 2 a.m. Pacific time on the dates you specify, so check what that means for your time zone. Choose CSV: saved search emails are cut off above 10,000 rows or 5 MB, and Oracle says “to include the maximum possible data, use CSV.” Emails with truncated results include a note about it.
7. Watch the CSV decimals. Oracle notes that in CSV exports “all decimal numbers are limited to 2 decimal places.” If your report uses exchange rates or unit costs with more precision, Oracle says to export to Excel first, then save as CSV.

What are your options?

If the search still needs more than three hours, or the email is cut off at 10,000 rows every month, move the data out of NetSuite on a schedule through scheduled CSV emails or SuiteAnalytics Connect, an add-on module you buy through your NetSuite account manager. Oracle says it is “not available for NetSuite Small Business accounts.” Changes inside NetSuite itself, such as custom fields, scripts or roles, belong with your administrator or a NetSuite partner.

Option	Good when	Watch for
Do it yourself	The search just needs to be lighter or run in the background	The spreadsheet rebuild often survives the fix
Buy a reporting tool	You want dashboards across many reports and can license the connection it needs	Someone still has to define every number so it matches NetSuite
Hire a freelancer	A NetSuite consultant can redesign the search, or a partner can change configuration	Changes inside NetSuite still run at month-end
Bring in an outside team (Fixes & connections)	The report needs NetSuite data plus your adjustments every month, without the wait	Needs your controller’s time to agree what “matches” means

Frequently asked questions