- 2 minutes to read

ContentSearchMaxScannedDocuments - System Parameter

New 7.12

ContentSearchMaxScannedDocuments is an integer System Parameter that limits how many documents a Regular expression search reads in Content Search: the Search content dialog for Articles, Snippets, Templates, and Document Profiles. The Web API reads it for every regular-expression search.

At a Glance

Property Value
Key ContentSearchMaxScannedDocuments
Data type integer (documents a regular-expression search reads)
Default 2000
Read by Web API
Takes effect At the next search when saved on the System Parameters page; within about 15 seconds in other processes, such as the MCP Endpoint; no restart needed
Status ✅ Active
Since Nodinite 7.12

How It Works

  • Words and Phrase searches narrow the documents in the database first. A regular expression can't be narrowed that way, so the search reads the newest ContentSearchMaxScannedDocuments documents and matches the expression against them.
  • When documents were left out, the line above the results says only the newest N documents were searched.
  • Every regular expression still has a one-second time limit; a slower expression is stopped, whatever this value.

See Content Search - Limits for all three limits together.

System Parameters page filtered on ContentSearch, showing ContentSearchMaxMatchesPerDocument 10, ContentSearchMaxResults 100, and ContentSearchMaxScannedDocuments 2000 with their descriptions (7.12)
Filter on ContentSearch to see the three Content Search limits together; this page covers ContentSearchMaxScannedDocuments.

Choosing a Value

Keep the default. When a regular-expression search reports that only the newest documents were searched, try Words or Phrase first: they search every document. Raise the value when your Repository has more documents than the limit and you rely on regular expressions; each such search then reads more documents and takes longer.

Next Steps