search returns no results" support triage

TL;DR

Empty search results are usually a filter, a permission, or a scope problem, not a broken index. Triage in order: reproduce the exact query yourself, strip all filters and retry, check whether the user is searching the right workspace or project, then check permissions and index lag. Nine times out of ten the content exists and something is hiding it.

The query

"search returns no results" support triage

Use this when

• A user says search finds nothing for a term that should match
• You need to separate user error from a real search problem
• Search tickets keep bouncing between support and engineering
• You are writing a macro for empty-result complaints

Not for

• Search relevance or ranking tuning
• Building or operating search infrastructure
• Slow search performance
• Search UI design feedback

Steps

1. Reproduce with the exact query

Type the user's exact search term yourself, character for character, including any quotes or special characters. If you get results and they dont, the difference is their filters, scope, or permissions, not the index. If you also get nothing, keep going.

Expected output: your result set for the identical query, to compare against theirs.

2. Strip every filter and retry

Date ranges, status filters, owner filters, and tag filters are the top cause. Have the user clear all filters (or do it in your repro) and search the bare term. Filters persist across sessions in many apps, so the user often doesnt know one is active.

Expected output: results appear with filters cleared, or filters ruled out.

3. Check the search scope

Confirm they are searching the right workspace, project, or tenant. Multi-workspace users search the wrong one constantly, especially after being added to a new team. Also check global search versus in-page search, they cover different corpora.

Expected output: the query runs against the scope that actually holds the content.

4. Check permissions

Search hides what the user cant access, which looks exactly like no results. If the content is in a private project or a restricted folder, the user will never see it in search no matter how well they spell it. Verify their access to the item directly, not just via search.

Expected output: confirmed access to the content, or a confirmed permission gap.

5. Check indexing lag and content state

Brand-new items can take minutes to hours to become searchable. Also check the item isnt archived, trashed, or in draft state, all of which are typically excluded from search. Ask when the content was created or last edited.

Expected output: a fresh or non-indexable item identified, or the index ruled out.

Ready-to-use reply

Let us track this down. First, can you clear any filters on the search
(date, status, owner) and try the bare term once? Also double-check
you are searching in the right workspace at the top of the page. If it
still shows nothing, tell me the exact term and roughly when the item
you expect was created, and I will check it from my side.

Variant phrasings

search isnt finding my document

Steps 3 and 4. Usually the wrong workspace or a permission gap.

no results for a term I know exists

Steps 2 and 5. Stale filters or an item too new to be indexed.

search worked yesterday, empty today

Steps 2 and 4. A filter got left on, or the user's access changed.

Why it happens

Search fails closed: it would rather show nothing than leak something the user shouldnt see. Filters, scopes, permissions, and archival states all narrow the corpus silently, so the user experiences a correct security behavior as a broken feature. Triage is really an exercise in finding which narrowing is active.

Edge cases

• Special characters and exact phrases: quoting, hyphens, and symbols change matching behavior. Try the plain words first.
• Stop words: very common words are often unindexed. Search the distinctive terms instead.
• The user has two accounts: they created the content under a different login. Check account, not search.
• Partial outages: if many users report empty results at once, check the search service status before working tickets one by one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstdYxkuwAolyX0T_Jm--0kw