Step 3 - Troubleshooting known issues when migrating to Security & Encryption Cloud
This page includes details of a number of known issues of secure macros that are not migrated to Cloud, together with possible solutions and workarounds.
Symptom in Confluence Cloud after migration | Cause | Solution/Workaround |
|---|---|---|
Secure macros appear on their relevant pages as
or
| These are Secure macros that are yet to be transformed. |
|
Secure macros appear in nested macros as
| Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited. In the example below, a Secret macro is nested within an Expand macro (a standard Confluence macro). This Secret would not be migrated unless it is moved out of the Expand macro.  Â |
|
Failed migration | The Security & Encryption for Confluence app user must have permission at space settings for the migration to be successful. |
In the example below, the app user should exist and have sufficient permissions.  |
Migration is incomplete | Secure macros belonging to owners with no product access to Confluence Cloud will not be transformed correctly to Cloud - this will result in the error Migration is incomplete. | Run through the steps below
|
Secure macros cannot be transformed if the Confluence administrator does not have Add page access to the target page where the Secret will be transformed to. This too will result in the error Migration is incomplete. | Run through the steps below
|