Vlocity Activation Errors Returned As Warnings

Problem

Some Vlocity components contain versions that are activated when the component is deployed. This can happen, for instance, with OmniScripts. The activation may fail when the component is deployed and, in this case, the Vlocity tool returns an error.

This error doesn’t mean that the deployment failed, it's just that the component deployed could not be activated in the destination org, and the Vlocity tool is notifying you about this. Copado displays the error in the same way it is returned to us by the Vlocity tool but, since the message is returned as an error, the deployment process in Copado is stopped, and the promotion branch is not merged into the destination branch.

Resolution

In order to prevent the deployment process from failing in Copado, and allow the promotion branch to be merged into the destination branch, Copado will regard this type of errors as warnings, and the deployment process will continue merging the promotion branch into the destination branch.

Please bear in mind that you will have to activate the component version manually in the destination org. This way, the entire deployment process (deployment and merge) will be completed.


How did we do?