Skip to main content
Card class: 🦸 HeroCategory: GL Health
Saved Searches hitting NetSuite’s processing timeout — blocks morning finance review queries. Tune filters or add indexes.

At a glance

Saved Search Timeout Rate (24h) is a gl health metric tracked from NetSuite data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture.
What it countsSaved Searches hitting NetSuite’s processing timeout — blocks morning finance review queries. Tune filters or add indexes.
Sample typeBackend API data from NetSuite, refreshed on the standard data refresh.
Why it mattersThe metric appears in the GL Health category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities.
Reading the valueCompare the current period to the prior period to read direction. Cross-reference siblings to triangulate cause.
Formatpercent
Time window24H
Alert trigger>5%
Sentiment key
Rolesowner, finance, engineering

Calculation

Calculated automatically from your NetSuite data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.

Worked example

A representative reading of Saved Search Timeout Rate (24h) for a typical NetSuite account. The card reports the current value alongside a comparison against the previous period — direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.

Sibling cards merchants should reference together

CardWhy merchants reach for it
ns_journal_imbalancesGL Health sibling: Transaction Imbalances.
ns_manual_journal_pctGL Health sibling: Manual Journal Entries as % of Total.
ns_suitescript_error_countGL Health sibling: SuiteScript Execution Errors (24h).
ns_journals_by_typeGL Health sibling: Transactions by Type.

Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard: find this metric (or its components) under the relevant report/section. Confirm the period boundaries and any filters match the Vortex IQ profile to reconcile cleanly. The Vortex IQ value may legitimately differ due to period definition, time zone, sampling, or how the vendor buckets the underlying records.