Version of newly imported Content Pack isn't changing after an update

Available Languages

Updated:September 29, 2026

Document ID:SPLK046840

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk IT Service Intelligence 4.17.0

Description

Issue:

Custom Content Pack created in a Test environment has version X
Content Pack gets deployed to a Production Environment
Content Pack gets installed with no issue (version X)
The same Content Pack is then updated in the Test environment
- It's version gets updated - version X1
Content Pack gets pushed from the Deployer to the Production environment
- the version in Production environment doesn't get updated - still remains version X

Investigation

Why this happens:

This Splunk environment is a Search Head Cluster as configuration is not push by the Deployer.
See Example in screenshot below from Search Head member:
- After Content Pack update in Deployer before push (example version X1)