Property reference

`glide.cmdb.group.max_ci_limit`

The glide.cmdb.group.max_ci_limit property sets the maximum number of configuration items (CIs) that can be included in a CMDB group. Admins should review this limit when they need to manage larger groups of CIs effectively, especially if they encounter restrictions on adding new items.

Default: Not stated
Type: Not stated
Application: Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property defines the upper limit for the number of CIs in a CMDB group, which is set to 10,000 by default.
What area does it affect?	CMDB Group Management
What does the default mean?	No default value is stated in the ServiceNow documentation.
When should you review it?	Review this property when planning to create large CMDB groups or when encountering limits on CI additions.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name	`glide.cmdb.group.max_ci_limit`
Type	Not stated
Application	Not stated
Default value	Not stated
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... does not exceed 10,000 records to avoid performance related issues. Note: The CMDB Group API doesn't support retrieving records exceeding 10,000 or the limit defined by the following properties. ◦glide.cmdb.query.max_results_limit ◦glide.cmdb.group.max_ci_limit To address this, these properties need to be adjusted to allow for larger query results if the CMDB query contains more records than the current limits permit. 3. Make sure ...

Brazil docs View supporting context

Context preview Snippet 2

... • To manually add CIs: asset or sn_cmdb_editor Also, to populate a CMDB group using a CMDB query, a saved CMDB query must exist. About this task The system property glide.cmdb.group.max_ci_limit determines the maximum number of CIs that a CMDB group can contain (by default 10,000). Once the specified limit is reached, CIs can't be added to the group unless you ...

More in `glide.cmdb`

Other properties in the same namespace.

glide.cmdb.data_manager.default_archive_time This property defines the default number of days before a Configuration Item is archived, influencing data lif glide.cmdb.data_manager.max_archive_time This property defines the upper limit for how long Configuration Items can be retained in the archive before b glide.cmdb.data_manager.rejected.task.notification_group This property configures the group that receives notifications when a task is rejected, ensuring relevant stak glide.cmdb.dataingest.enabled This property enables or disables the CMDB Data Ingestion API, impacting how data is ingested into the CMDB. glide.cmdb.health.autoCloseAuditTasks When enabled, this property ensures that audit tasks related to deleted cmdb_health_result records are automat glide.cmdb.health.ci_ownership_field This property defines the field used to identify the ownership of configuration items in the CMDB, impacting h glide.cmdb.health.metricProcessor.maxRunningTime This property limits the execution time of individual metric processors, ensuring they do not run longer than glide.cmdb.health.services.max_level This property limits the number of CI relationship levels that can be traversed when determining associated CI

All 57 properties in glide.cmdb →