---
sourceDocument: Zurich ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/platform-administration

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Indexed source guardrails

# Indexed source guardrails {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 2, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Indexed source guardrails

Indexed source guardrails in AI Search help reduce the index size and improve search performance by limiting the number of task and alert source records indexed from large tables such as Task \[task\] and Alert \[emalert\].
These guardrails prevent excessive indexing of records, which can negatively impact both indexing speed and search response times.
By default, AI Search indexes up to 10 million records for each of these tables and their child tables.
Show full answer Show less  

## How Guardrails Work

* AI Search first checks the Guard Rail Limit for Indexed Data Sources table to determine if a maximum record count is defined for an indexed source.
* If no entry exists, the system property **glide.ais.ingestion.guardrailsenableddatasources** is checked for a limit.
* If no limits are found, no guardrail is applied to that source.
* Guardrail limits are applied after filtering records based on indexed source filter conditions and retention policies.
* AI Search indexes the most recently modified records; older records are discarded if the limit is exceeded.

## Modifying Guardrail Settings

ServiceNow personnel can modify guardrail configurations for your instance by:

* Overriding default record-count limits for Task and Alert tables.
* Creating custom guardrails for other source tables.
* Disabling guardrails if needed.

Note that changes to guardrail settings may take up to 24 hours to affect indexing behavior.

## Search Performance Considerations

Several factors controlled by customers influence AI Search performance related to indexing:

* **Index size:** Larger indexes take longer to search. Avoid indexing unnecessary content.
* **Number of indexed sources:** More sources increase search time even if index size is constant.
* **Number of indexed fields:** Indexing more fields slows down search independently of size or source count.
* **Indexing frequency:** Frequent updates increase competition for compute resources, reducing search responsiveness.

## Indexed Source Retention Policies and Filter Conditions

To optimize index size and update frequency, you can define retention policies and filter conditions for indexed sources:

* **Retention policies** exclude older records (e.g., records older than two years) to keep search results current and reduce index size and update frequency.
* **Filter conditions** exclude records based on criteria like status (e.g., excluding records with status Open), reducing indexed records and update frequency.
* AI Search uses these settings to automatically purge stale records from the index.
* Retention policies are mandatory for sources indexing records from Task \[task\] or its child tables, and optional for other sources.  
Reduce index size and increase search performance with guardrails that limit the number of task and alert source records indexed from indexed sources.

## Guardrails overview {#indexed-source-guardrails-ais__section_j3b_j1q_vcc}

The Task \[task\] and Alert \[em_alert\] tables and their child tables contain large numbers of records. Indexing the full set of records from these tables for search increases the size of the AI Search index and can impact performance for indexing and search.

To reduce index size and preserve indexing and search performance, AI Search applies guardrails when indexing records from these tables. These guardrails limit the maximum number of records that can be indexed from the Task and Alert tables.

Guardrails are enabled in the base system for the Task and Alert tables and their child tables. By default, AI Search indexes a maximum of 10 million records for each of these tables.

## How guardrails work {#indexed-source-guardrails-ais__section_q2y_rcq_vcc}

When guardrails are enabled, AI Search first checks the Guard Rail Limit for Indexed Data Sources \[`ais_guard_rail_limit_data_source`\] table to see whether a record exists for the indexed source (defining the maximum number of
records to index for that indexed source). If no table entry exists, AI Search checks the `glide.ais.ingestion.guard_rails_enabled_datasources` system property value to see whether a limit is defined there for the indexed source. If no limit is found in either place, AI Search does not apply guardrail limits to the indexed source.

Guardrail limits on the number of records indexed are applied after the set of source records is limited by the indexed source's filter conditions and retention policy. For details on indexed source filter conditions and retention
policies, see [Indexed source retention policies and filter conditions](https://www.servicenow.com/docs/WlmYUuk1IlpdDh2VuW7eyg "To limit the set of records indexed from source tables, you can configure retention policies and filter conditions for your indexed sources. AI Search also uses these settings to automatically purge stale records from the index, optimizing search performance.").

AI Search always indexes the most recently modified records from the indexed source table. If indexing causes the record count for the table to exceed the guardrail limit, AI Search discards older records from the index to make room for the newer records.

## Modifying guardrail settings {#indexed-source-guardrails-ais__section_lqg_p1q_vcc}

A ServiceNow® employee can modify guardrail settings for your instance as follows:

* Override the base system record-count limits for the Task and Alert table guardrails
* Create custom guardrails to limit the maximum number of records indexed from other source tables
* Disable guardrails

{#indexed-source-guardrails-ais__ul_iw3_t2q_vcc}  
Note:  
Changes to your instance's guardrail settings may take up to 24 hours to be reflected in AI Search's indexing behavior.

## Search performance considerations for indexing {#indexed-source-guardrails-ais__id_bzn_2b1_5jc}

Search performance for AI Search is affected by several customer-controlled factors related to content indexing. Changes to these factors can impact search performance as follows.

Index size
:   Indexing more content produces a larger index, which takes more time to search. Avoid indexing content that isn't needed for search.
:   Indexing large source tables, such as the Task \[task\] table and tables that extend it, can add significant numbers of records to the AI Search index.

Number of indexed sources
:   An index with more indexed sources takes longer to search than one with fewer indexed sources. This is true even if the two indexes are the same size.

Number of indexed fields
:   Increasing the number of fields you index across your indexed sources makes the system take longer to find search results. This effect is independent of index size and number of indexed sources.

Indexing frequency
:   The more often your indexed content is synchronized and updated, the more often search will compete with indexing for compute resources, increasing search response time. This is especially pertinent for indexed sources
    with frequently modified fields.

## Indexed source retention policies and filter conditions {#indexed-source-guardrails-ais__id_k3x_fc1_5jc}

To limit the size of your index and the frequency of index updates, you can define retention policies and filter conditions for your indexed sources.{#indexed-source-guardrails-ais__retention-policies-filter-conditions-p1}

As an example, you can define a retention policy for an indexed source to exclude records that are more than two years old. This policy keeps your search results more current and
reduces the size of your index. Changes made to the excluded records don't trigger index updates, so this policy also reduces indexing frequency.{#indexed-source-guardrails-ais__retention-policies-filter-conditions-p2}

Similarly, you can define a filter condition for an indexed source that excludes source table records with a specific status, such as Open. This filter condition reduces the number of
records indexed from the source table, which in turn reduces the total amount of data you index. Excluding open records that have frequent updates also reduces indexing frequency.{#indexed-source-guardrails-ais__retention-policies-filter-conditions-p3}

AI Search also uses your retention policy and filter condition settings to automatically purge stale records from the index, reducing its size.{#indexed-source-guardrails-ais__retention-policies-filter-conditions-p4}

To learn more about creating retention policies and filter conditions for your indexed sources, see [Indexed source retention policies and filter conditions](https://www.servicenow.com/docs/WlmYUuk1IlpdDh2VuW7eyg "To limit the set of records indexed from source tables, you can configure retention policies and filter conditions for your indexed sources. AI Search also uses these settings to automatically purge stale records from the index, optimizing search performance.").{#indexed-source-guardrails-ais__retention-policies-filter-conditions-p5}  
Note:  
Retention policies are required for indexed sources that index records from the Task \[task\] table or tables that extend it. They are optional for other indexed sources.