Deployment failed

This topic describes scenarios that can cause the deployment to fail. After the issue has been corrected, you must run the deployment again.

Import fails due to unresolved validation errors

The import can fail if the package is imported without first resolving blocking validation issues, such as missing dependencies, invalid parameter values, or conflicting configuration. To correct this, review and resolve all errors reported during the validation step for the same package and tenant. Ensure that prerequisite global packages are deployed, parameter values are valid for the target WFM configuration, and any conflicts with existing configuration are addressed. After validation completes successfully, retry the import.

Import fails because of missing or corrupted package artifacts

The import can fail if the global package artifacts are missing, incomplete, or corrupted in the repository, for example when the export did not complete successfully or the package version was changed or deleted after it was selected for deployment. To correct this, verify in CloudSuite Portal that the package version has a successful build status and that all related artifacts are available. If needed, re‑export the package version from the editor tenant, ensure the export step completes successfully, and then attempt the import again using the newly exported version.

Import fails due to data or configuration conflicts during write-back

During import, the package may fail when WFM attempts to create or update configuration that conflicts with existing tenant data, even if validation did not treat the issue as blocking. Examples include unique key violations, unexpected existing records, or environment‑specific constraints that are enforced only at write time. To correct this, review the detailed import error messages to identify which object or table failed. Adjust or remove the conflicting configuration in the target tenant, or, if appropriate, adjust the package parameters or contents so that new configuration uses non‑conflicting identifiers. After resolving the conflict, rerun the import.

Import fails due to permission or connectivity issues

The import can fail if the service account or process used for deployment does not have sufficient permissions in WFM or if there are connectivity issues between CloudSuite Portal and the target tenant. To correct this, confirm that the deployment is being run with a role that has the required administrative and integration permissions, and verify that the WFM tenant is available and not in maintenance mode. Resolve any connectivity or authentication issues reported in the error details, then restart the import.

Import fails due to environment version or feature mismatch

The import can fail when the target tenant is running an older or incompatible WFM or suite version that does not support certain objects or features included in the package. To correct this, compare the target tenant version with the documented minimum version or feature set required for the package. If the tenant is behind, upgrade WFM or enable the necessary features first. Once the environment meets the required level, repeat the import using the same package version.

Note: 
  • Import can fail when parallel deployments of different packages under the same namespace are triggered on the same target tenant.
  • Import can fail when parallel deployments of different packages under different namespaces are triggered on the same target tenant.