Property reference

sn_sec_cmn.background_job_max_concurrency

The sn_sec_cmn.background_job_max_concurrency property sets the maximum number of background jobs that can run in parallel. Admins should review this setting to optimize performance based on their instance's node count and job requirements.

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 directly controls the concurrency level of background job processing, allowing for adjustments based on system capacity and job types.
What area does it affect? Background job processing
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review this property when adjusting system performance or when changing the number of nodes in your instance.

Property record

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

Property name sn_sec_cmn.background_job_max_concurrency
Type Not stated
Application Not stated
Default value Not stated
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... begin Role required: sn_vul.vulnerability_admin, or Vulnerability managers with the sn_sec_cmn.manage_background_job granular role Note: This procedure requires advanced programming knowledge. Procedure 1. In the Filter navigator, enter sys_properties.list and locate the sn_sec_cmn.background_job_max_concurrency system property. 2. Click it to open the record. By default, the sn_sec_cmn.background_job_max_concurrency system property executes a maximum of 10 background jobs in parallel. If your instance has a low ...