Email Properties Not Preserved After Instance Clone Despite Data Preservers and Exclusions

[sahajags]

Hello everyone,
We recently cloned our production instance to our development instance. I added both sys_email_account and sys_properties to the data preservers and exclusions in the clone profile.
After the clone completed, I noticed that the email properties were still unchecked. What could be causing this? Has anyone encountered this issue?

[Dr Atul - LNG]

1. Email properties are part of sys_properties, you can preserve that table in source instance.

2. sysevent can be excluded. in source instance.

Refer : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717012  

[RaghavendraGund · Accepted solution]

Hello @sahajags 

Even though you included the sys_email_account table and sys_properties table in both preservers and exclusions on the clone profile. email sending enabled and email receiving enabled are unchecked, because the reason would be the "Disable emails" script   in cleanup  scripts, which is a OOB script. clean scripts run after the completion of the clone. this script runs, which makes those 2 properties to false. if you want you can remove this "Disable Emails" script from the clean up scripts. But, my suggestion is to keep the disable emails on the clean scripts and after the clone, as post clone step, you can manually turn those 2 steps back on.

Refer Attached Screenshots please

Regards
Raghavendra G