Deployment failed

Schema exists in the target tenant as a different type

If one or more schemas in your package already exist in the target tenant as different types, those resources fail on import. The package's remaining resources are imported successfully unless otherwise stated.

To correct this issue, delete the existing resources in the target tenant and redeploy the package.

Stream pipeline exists and is running in the target tenant

If one or more stream pipelines in the package already exist and are running in the target tenant, those stream pipelines fail on import.

To correct this issue, you can stop the existing stream pipelines in the target tenant and redeploy the package.

Stream pipeline exists in the target tenant with a different object name

If one or more stream pipelines in the package already exist in the target tenant with a different object name, those stream pipelines are deployed but object names are not updated. An object name cannot be changed on a stream pipeline that was active at least once.

To correct this issue, you can delete the existing stream pipelines in the target tenant and redeploy the package.