Troubleshooting known issues when migrating to Page Approval Cloud

This document highlights common problems that may occur during the migration process to Page Approval Cloud and provides possible solutions.

Erros/Issues

Cause

Solution

Erros/Issues

Cause

Solution

Page Approval remains stuck at 0%.

 

When installing Page Approval in Confluence Cloud, an app user is added to your Confluence user group.

If the confluence-users group is not defined as the default access group, the app user is not added.

As a result, the migration process is stuck at 0% progress.

  1. Go to admin.atlassian.com and select an organization.

  2. Select the Products tab from the top navigation bar.

  3. Under Actions, Click Manage Product for the Confluence product.

  4. Find the confluence-users entry from the group list and click the three dots menu. From the dropdown, click Update default group setting.

  5. In the window, select User and click Update. The default group section will have a tick mark similar to the screenshot below:

  6. Next, reinstall the Page Approval app in Confluence Cloud. Reinstalling adds the app user to the confluence-users group.

  7. Run a new migration to verify if the Page Approval content can be successfully migrated to Confluence Cloud.

  8. If the issue still persists, reach out to our customer support team.

Page Approval app migration remains stuck at 30%

 

This is due to page restrictions on pages with Page Approval macro. Currently CCMA (Confluence Cloud Migration Assistant) does not support migration of app data on restricted pages.

This is a known bug (MIG-837) with the Atlassian migration tool.

  1. Ensure that any page using Page Approval has no page restrictions

  2. To find the list of restricted pages:

    1. Visit the Space > Space tools > Permissions > Restricted Pages

  3. Remove all the restrictions until the list is empty for those pages that are using the Page Approval macro.

  4. Run a new migration using CCMA by following this guide (If the space was migrated to Cloud previously but failed, it must be deleted from Confluence Cloud first).

 

Â