When a suite product tries to update an asset that it previously created in CentraSite, the update fails if the asset is locked due to a pending activity at the CentraSite level. This can happen, for example, if a CentraSite policy related to the asset has been triggered that requires an approval action and the approval has not yet been granted.

Example: A user publishes a package from the Designer UI and this publish creates a service among other things in CentraSite. Then a CentraSite user with appropriate permissions tries to change the lifecycle state of this service and this triggers a policy you have defined for the service. If this policy has an approval action, then as long as the approval is pending no-one can edit this asset. This is according to design and is the same for all asset types (both suite and otherwise). If the user now tries to publish the package again, the publishing logic will try to edit the service and fails since CentraSite does not allow edits. The policy can be triggered by a CentraSite user as well. Basically if you have a policy for the specific asset type with approval action, you may run into this situation.