Validation failed
This topic describes scenarios that can cause the validation to fail. After the issue has been corrected, you should run the validation process again to verify that all issues have been corrected.
Missing prerequisite global package
Validation fails when the deployed package depends on another global package version that is not yet present or not activated in the target tenant. To correct this, review the package’s documented dependencies and ensure all prerequisite global packages are deployed and activated in the correct order. After the prerequisite packages are successfully deployed, rerun validation for the original package.
Unsupported or missing WFM configuration references
Validation can fail if the package references WFM configuration that does not exist or is not supported in the target tenant, such as org units, pay groups, calendars, or labor metrics. To correct this, identify the missing or incompatible references in the validation message, create or adjust the required WFM configuration in the target tenant, or update the package parameters to point to valid WFM objects. Then run validation again.
Invalid or incomplete package parameter values
If required package parameters are left blank, use invalid formats, or point to incorrect WFM objects, validation will fail. To correct this, review the list of parameters for the package, confirm which fields are required, and enter values that match the target tenant’s configuration and data standards. Avoid copying values from other environments without checking that they exist in the target tenant. Once corrected, repeat the validation.
Conflicting existing configuration in the target tenant
Validation may fail when the package attempts to create or update configuration that conflicts with existing items, such as duplicate codes, names, or keys for WFM rules, groups, or templates. To fix this, review the conflict details in the validation output, then either rename or adjust the existing configuration, or adjust the package contents or parameters so that the new configuration uses unique identifiers. After resolving the conflict, run validation again.
Version or compatibility mismatch
If the target tenant is running an incompatible application version or lacks required features, validation can fail because the package assumes capabilities that are not available. To correct this, confirm that the target tenant’s WFM and suite versions meet the minimum requirements documented for the package. If they do not, plan and apply the necessary product updates or choose a package version that is compatible, then repeat the validation.
Data quality or mandatory data issues
Some packages rely on baseline data being complete and valid in the target tenant, for example reference data used by rules or calculated fields. Validation can fail if mandatory data is missing or inconsistent. To correct this, use the validation details to identify which table or entity is affected, clean up or complete the underlying data in WFM or the related application, and then rerun validation to confirm that the package can be applied successfully.