Property reference

`glide.discovery.delete_strategy.max_related_entries_delete_in_iteration`

Limits the number of related entries a deletion strategy processes in each iteration. The default of 500 caps each batch at that many entries, while higher or lower values change the batch size.

Default: 500
Type: integer
Application: Not stated
Category: CMDB & Discovery

Key questions about this property

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

What does it do?	Sets the maximum number of related entries the deletion strategy handles in each iteration, defaulting to 500.
What area does it affect?	Discovery deletion strategy
What does the default mean?	The default value is "500", which sets the baseline numeric behavior for this property.
When should you review it?	Review when adjusting how many related entries are handled in each deletion iteration.

Property record

No out of the box record exists. ServiceNow scripts read this property and use the default value shown until you create it.

Property name	`glide.discovery.delete_strategy.max_related_entries_delete_in_iteration`
Type	integer
Application	Not stated
Default value	`500`
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Used in

Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.

Script include: AbstractDeleteStrategy This setting limits how many related entries the deletion process handles in one iteration, allowing administrators to adjust the amount processed at a time. If no value is set, the default is 500. /sys_script_include.do?sys_id=591e87c1db690010690cf9c31d9619f7

Script include: CustomDeletionStrategyUtils The deletion strategy reads this setting to limit how many related entries it deletes in each iteration; admins can change that limit, and the default is 500 if no value is configured. /sys_script_include.do?sys_id=f4b6848a47b2f5902a0cb66c416d430d

Delete Strategy: AzureDefaultDeleteStrategyVM This setting controls the maximum number of related entries the Azure VM delete strategy processes for deletion in one iteration; administrators can change that limit. If the setting is not configured, the code uses 500. /sn_discovery_delete_strategy.do?sys_id=46029b1c87893d10231aedb73cbb353a

More in `glide.discovery`

Other properties in the same namespace.

glide.discovery.delete_strategy.ci_batch_size_for_deletion Sets the number of configuration items grouped into each deletion batch, defaulting to 500 when no value is… glide.discovery.delete_strategy.max_ci_before_triggering_batch_deletion Sets the number of configuration items that must be selected before the deletion strategy triggers batch… glide.discovery.delete_strategy.max_ci_search_group Sets the maximum number of configuration items grouped in each search during deletion processing, defaulting… glide.discovery.delete_strategy.max_deletion_records Sets the maximum number of configuration item records that deletion strategies can delete, defaulting to… glide.discovery.device.duplicate.ip.optimization When enabled, Discovery can treat a device as a duplicate if its IP belongs to a configuration item with… glide.discovery.disable_mid_probe_cache This property controls whether the MID server caches probe parameters, affecting how frequently updated… glide.discovery.disable_next_hop_data This property controls whether the Next Hop Routing Rule table is populated during the discovery of… glide.discovery.discover_aws_ec2_host_metadata This property allows probes to collect AWS EC2 metadata when discovering hosts via IP.

All 168 properties in glide.discovery →