Forge bulk-update: Failed upgrade, any way to investigate

We released a new version of our app, and used ‘forge version bulk-upgrade’. This worked for the majority of the installations. All installations did the same version step.

However, for installations it fails and they are stuck on the old version. While this works, over time these installations probably will break.

Is there any way to find out why a bulk-upgrade failed?

Ok, out of the 25 failed upgrades 24 don’t have an active license. So, maybe that’s the main reason.

I hope if these customers consider re-activating the license, that they then upgrade.

1 active licensed installation only fails to upgrade.

I opened a ticket recently with ECOHELP for a problem with similar symptoms, and their response was:

I have verified the backend logs and found that the bulk upgrade is failing on those sites because the Confluence product is in a suspended/deleted state.