Skipped records reconciliations missing after applying upgrade plan.

[Christopher Sik]

We have been using upgrade plans for the last few months to manage our scheduled upgrades.
1) We create the upgrade plan in DEV.

2) We reconcile any skipped records in DEV using the Upgrade Monitor.

3) We refresh the upgrade plan and publish it. 

4) We go to our TEST instance and retrieve the upgrade plan.

5) In TEST we install the upgrade plan.

6) In TEST we review the Upgrade Monitor. (This is where we run into the problem.)

We're noticing that most of the skipped records we reconciled in DEV still show up as unreconciled after we apply the Upgrade Plan in TEST. The same thing happens when we apply the Upgrade Plan to PROD.

I thought the point of the Upgrade Plan was to avoid the need to manually re-reconcile the same skipped records in each instance.

I expect some variation in the count of skipped record between instances due to development in the platform and the time span between clone downs. And from patch to patch or hotfix to hotfix, there aren't usually that many records to review. So having to re-reconcile 20-30 records isn't such a big deal.

But this month we opted to jump from Tokyo to Vancouver and had close to 200 skipped records to work through. That took a couple of weeks to get through. We added detailed notes to each record, merged a large number of them, reverted a good chunk of them too. But all that reconciliation is not showing up in TEST after applying the upgrade plan.

Is anyone else encountering the same issue? Is there a setting or step that we're missing?

[Christophe_E]

Additional information from the support: "Skipped records belonging to records present in scopes that are not manageable via application repository would not be handled by Upgrade Plan."

[dmorgan_isc]

I am facing this exact issue, was it ever resolved?
i followed:
1. Upgrade DEV

2. review skippedrecords in DEV

3. build plan in DEV

4. publish

5. Retrieve in TEST

6. Even though its retrieved and active and ready, i can not preview with this upgrade plan

7. TEST upgraded, none of the reviewed records were captures, all need to be reviewed again.

[christophenow]

Hello,

No, my Incident was created 2024-03-27 and is still open.

You need to open an Incident on your side also.

And with the time passing, and the automated patching, there is a very high risk that the upgrade plan (done on Dev) is no more alligned with the current Test instance.

I will update you when I got a resolution. Our upgrade on Prod is still pending for this reason.

Regards,

Christophe

[dmorgan_isc]

We finished our upgrade on PROD on the weekend and the good news is the Ugrade Plan did apply.

I noticed that while the upgrade plan did not show in the upgrade preview,  if i browse to the preview table list view, i could see it there (i could tell by the timestamp it was the one run as part of applying the upgrade plan - hope that makes sense).

Further SN have commented:

PRB1672398: Upgrade plan is not used while generating the upgrade preview. PRB is fixed in Vancouver and Washington DC release.
Below is the workaround suggested on the PRB:
A. Update the upgrade plan's target_version extension from .zip to .war in the sys_upgrade_plan table and then generate the upgrade preview. Set the workflow to false while updating the target_version so that business rules do not run.
B. Once the preview is generated, update the target_version back to .zip. This is important because if the target_version is not updated back to .zip then the upgrade plan will not be consumed during the upgrade.

good luck