When Space XML Imports Fail, Partial Space Data is Left in the Database

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)