Upgrade preview no longer working in dev instance after clone

[Brian Lancaster]

I'm trying to run an upgrade preview after cloning production in dev. It was working before but is not longer working. I added the dev URL to the system property "Remote instance record ID of a non-production instance to query upgrade duration estimate." but it is still not working. Any thoughts on what else I may need to do?

[Mark Roethof · Accepted solution]

Hi there,

If the sys_property "glide.upgrade.preview.duration.instance.id" has a value, it checks here first. This value should be the sys_id of the remote instance.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Brian Lancaster]

How do you get the sys_id of your instance?

[Mark Roethof]

Navigate to the remote instances table:

Team Development > Remote Instances

And copy the sys_id of your remote instance there.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Mark Roethof]

Can't reproduce at the moment, no instance for it. Though copy/paste from a Support Case on this subject from may 2021:

"Most Probable Cause:
The part of the execution that gets stuck on this page is related to the system checking externally for the estimate on how long the upgrades will take.

Which external source the Upgrade Engine checks is based on a few things:
- If the sys_property "glide.upgrade.preview.duration.instance.id" has a value, it checks here first. This value should be the sys_id of the remote instance.
If we click on the record, we can see Value is empty :

https://<your-instance>.service-now.com/nav_to.do?uri=%2Fsys_properties_list.do%3Fsysparm_query%3Dname%253Dglide.upgrade.preview.duration.instance.id%26sysparm_first_row%3D1%26sysparm_view%3D

- Otherwise, the system will check every instance in the Remote Instances list (sys_update_set_source table).

Solution Proposed:
1) I believe if you add the instance's sys_id to the glide.upgrade.preview.duration.instance.id property, it will resolve the issue.
This is how you can find an instance's sys_id:
- Navigate to the sys_update_source table

https://<your-instance>.service-now.com/nav_to.do?uri=%2Fsys_update_set_source_list.do

- Open a record
- Right click on header - Show XML
- View the "instance_id" value

2) It may also be worth verifying every connection in the sys_update_set_source table as well. You can do this by clicking "Test Connection" on each of the sys_update_set_source records.

Please review this KB for further details:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0959684"

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list