Be honest: how do you answer "when was this sub-prod last cloned?" today?
If the answer involves logging into four instances, a spreadsheet, or pinging whoever cloned it last, this post is for you.
Multi-Instance View, in one line
The Clone Admin Console now shows clone activity and cleanup script status across all your connected instances from a single console, instead of one instance at a time.
Two things you get immediately:
- Last-cloned timestamps on the Instance Overview page → see at a glance which environments are drifting from production, so you can plan refreshes
- Unified progress for cleanup scripts running on the target → you know whether post-clone automation actually finished, without chasing it instance by instance or digging through logs (new in Australia Patch 5)
Together, clone becomes something you manage across an estate, not something you check one instance at a time.
Turning it on
- Upgrade to Australia Patch 5 — cleanup script progress requires AP5 on both source and target
- Opt in via Clone Home > Configuration > Multi-Instance View
- Connect all your sub-prod instances
The Instance Overview and Clone Activity pages then fill in, and both let you view all clones or filter to specific source instances via a dropdown. You get Multi-Instance View across your instance estate, plus cleanup script status right on the clone status page - with more on the roadmap.
If you turn it off, you will need to redo the trust config flow with your instances to turn it back on.
Simplified OAuth authentication
OAuth replaces the old local admin requirement. No local admin credentials to create, store, or rotate. One pairing ceremony, then you're done. Basic Auth remains as a fallback. Link to clone authentication documentation.
Also in recent releases
- Clone FAQ Agent (2.2.1, Australia Patch 2) - ask clone questions in your instance, answered from curated ServiceNow clone documentation and KBs (requires a Now Assist license). If Now Assist was installed after the Clone Admin Console, reinstall the console from the Store to enable the skill.
- Estimated clone completion time with a relative indicator ("in 2 hours," "in 2 weeks")
- All settings consolidated under a single Configuration menu
- A dedicated Help page
- Submit a new clone request even when a future clone already exists for that target (as long as they're more than five days apart)
Then tell us how it went 👇
What's the first thing you noticed once you could see every instance at once? Anything missing from the view you'd want next? We read every comment, and it shapes what ships.
