System Clone always disables email sending/receiving in the target instance - Known Error

System Clone always disables email sending/receiving in the target instance Description Post the clone, email properties are always getting disabled in the target instance even after deactivating the clone cleanup script "disable emails" in both the source and target instances.

Steps to Reproduce

1> Disable/deactivate the clone cleanup script "Disable emails" in the source instance

2> Set the below properties to true in both the source and target instances

glide.email.read.active glide.email.smtp.active

3> Schedule the clone

4> Post the clone check in the target instance and the above properties will be set to 'false'

Workaround Email must be disabled on clone target instance after clone to avoid unexpected emails being sent out. We won't change this behavior.

If you need email send/receive enabled on the target instance post the clone. Please follow the below suggestion.

1) create a new post clone script on the source (target instance optional): Script name: Enable email

2) Add the below logic in the script and save the cleanup script and ensure, it is activated to run.

gs.setProperty("glide.email.read.active", true); gs.setProperty("glide.email.smtp.active", true);

Post the clone completion, the email properties will be set true in the target instance.