UI11 gets activated and roles become no longer effective on a target instance after a cloneIssue When an instance is cloned over, some times it happens that the UI changes to UI11 though the source UI is UI16/UI15. Other symptoms include: The users with admin roles, will not be able to access all modules. They will only see the self-service view. The roles are not effective on the instance.Users will not be able to see impersonate options as well. ResolutionImmediate relief can be achieved by performing the rollback of the clone.The issue encountered is when the sys_properties table is added to the clone excluders listThe sys_properties table extends sys_metadata and the clone functionality does not support excluding tables that are extended.Following the clone, there will be ghost records on the sys_metadata table and this will prevent the preserved records for core properties from being imported back to the instance after the clone.This will result in a cloned instance without vital properties such as the UI properties.Please remove the exclude rules for sys_properties and then schedule a new clone for at least 36 hours from then.This will ensure enough time has passed for the new exclude rules to take effect. Related LinksPlease refer to the following documentation thoroughly before configuring any clone preserve or exclude rulesExclude a table from cloningData preservation on cloning target instances