Clone from Production to Development Fails at “Applying Preservers” with “Intervened” Status (around
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
We attempted to clone our Production instance to Development, but the clone failed at the “Applying Preservers” stage with status “Intervened.” Could you advise on how to troubleshoot the root cause?
（Message: Clone stage changed from Applying Preservers to Intervened)
Environment:
Source: [prod subdomain]
Target: [dev subdomain]
Observed Behavior:
Progress stops at about 66%, and stage transitions as follows: “Restore → Applying Exclusions → Applying Preservers → Intervened”
UI shows: Clone Status: Error — “Error Occurred. Please contact support”
In sys_clone_log, an error occurs immediately after “Applying Preservers” (details below).
Main Preserver Targets (excerpt):
Accounts & Roles: sys_user, sys_user_group, sys_user_has_role, sys_user_grmember, sys_user_role, sys_user_role_contains
Access & Authentication: ip_access, acr_user, sys_properties (glide.sso.acr*), etc.
Business Data: pm_project, pm_project_task, pm_portfolio, risk, issue, rm_epic, rm_story, rm_sprint, rm_scrum_task, service_offering, cmdb_ci_service, etc.
Large Tables: task, sys_journal_field, sys_audit, sys_attachment
Configuration Updates: sys_update_set, sys_update_xml
We have also opened a Now Support case (low priority) but have not yet received a response. This issue is urgent because an upgrade is scheduled soon and, due to the error on Now Support, we cannot change the upgrade schedule ourselves.
Could you provide guidance or recommended steps for isolating the cause of a clone failure at “Applying Preservers”?
Thank you in advance.
