-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 3.5.16, 4.3.7, 5.3.1, 5.7-OD-47, 6.2.0, 6.2.4, 6.3.1, 7.4.4, 8.5.3
-
Component/s: Space - Export / Import
-
128
-
Severity 2 - Major
-
33
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Space XML imports will sometimes fail due to a variety of reasons:
- Confluence runs out of memory
- The import process times out
- Unique key constraint violations
- A few other causes are described in https://confluence.atlassian.com/display/DOC/Troubleshooting+XML+backups+that+fail+on+restore
Oftentimes these partially imported spaces remain in the DB without any way to remove them via the UI, making a re-import attempt impossible (due to a duplicate Space Key or other constraint violation).
Can we investigate:
- some way to rollback a failed XML space import (or determine whether imports will fail before it starts)?
- possibilities for Confluence to automatically recognise half-imported Spaces and delete related data from the UI?
Current workaround: How to Manually Delete a Space (Cloud users will need to contact Atlassian Support and request removing the Space from Confluence database)
- duplicates
-
-
- Closed
-
- has a derivative of
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
JST-133598 Loading...
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-