Recently we have been migrating our Connect apps to Forge; and as part of this process we have needed to use forge version bulk-upgrade to move customers from our Connect version to our Forge version.
When we did this for our first app (with the fewest number of total installations), every installation upgraded successfully. Running forge version bulk-upgrade list reported “0 pending” and “0 failed” installations, including both active and inactive license states.
For our second app, the vast majority of installations upgraded successfully, but not all. Running forge version bulk-upgrade list reports “4 failed”. Repeating the bulk upgrade multiple times has not been successful in getting these last 4 installs upgraded.
All four of those failures are for installations where the license status is inactive (yet many other installs with inactive licenses did upgrade successfully).
The fact that these are all inactive gives us some comfort, however as we’re looking to switch off our old Connect infrastructure we are concerned about these installs that remain on our Connect version.
I realise this might be a difficult question to answer in a general sense, but what would be some reasons why an upgrade fails; and is there any way to troubleshoot failures when using the bulk-upgrade tool?