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.
At this time, there are no known validation failures, however, you may see the Evaluate status returned for some resources.
Object schema exists with the same name, but different type
If an object schema with the same name exists in the target tenant as a different object type, the Evaluate status is returned.
To resolve the issue, you must accept and acknowledge the warning before proceeding with the deployment. If the existing schema is no longer required, you can delete it from the target tenant before proceeding with the deployment.
Schema extension is in use by another schema file
If a schema extension included in the package is using a different schema file in the target tenant, the Evaluate status is returned.
To resolve the issue, you must accept and acknowledge the warning before proceeding with the deployment. If the extension is no longer required in the target tenant, you can remove it from the tenant before proceeding. If the schema extension is not removed from the target tenant, the extension in the file is skipped and will not be imported.
Stream pipeline exists and is running in the target tenant
If a stream pipeline already exists in the package and is running in the target tenant, the resource can't be overwritten in the target. The import of that stream pipeline fails.
To resolve this issue, stop the existing stream pipeline in the target tenant. Otherwise, the package resource isn't deployed to the target tenant. All other issue-free resources are imported successfully.
Stream pipeline exists in the target tenant with a different object name
If the package's stream pipeline already exists in the target tenant but with a different object name, the object name can't be overwritten in the target tenant. Object names can't be changed for stream pipelines that have been active at least once. As a result, the import succeeds, but the object name isn't updated.
To resolve this issue, delete the existing stream pipeline in the target tenant. Otherwise, the package resource is deployed but the object name isn't updated. All other issue-free resources are imported successfully.