Retained key constraint after failed deployment

We have tried to deploy from one environment to another which consisted of a changed delete rule/foreign key constraint to one of an entity's attributes. The deployment failed due to some error but the changed delete rule was carried over to the target environment.

As per our understanding, if a deployment fails, changes from the origin environment won't be carried over and the target environment will retain its current version. However, as per our client, the changed delete rule was carried over regardless.

Is this to be expected or the delete rule was supposed to be rolled back? And if we do deploy again, would there be any issues regarding the constraint matter?

Thanks in advance.

Not expected. Somehow the SQL scripts around Delete rule were not covered in the rollback plan it seems. Better to report this using the feedback option on Service Studio and additionally raise a support ticket for further investigation.

Tushar Panpaliya wrote:

Not expected. Somehow the SQL scripts around Delete rule were not covered in the rollback plan it seems. Better to report this using the feedback option on Service Studio and additionally raise a support ticket for further investigation.

Will do. Thanks!