-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Space - Import from other tools (3rd party)
-
None
-
2
-
Severity 2 - Major
Problem Description
Notion import in Confluence fails due to improper handling of the integration token. During the import operation, page retrieval via Notion API results in a 404 error because the token loses access permissions midway through the import.
In the backend logs, you may see one of the following errors:
io.atlassian.micros.instant.exceptions.NotionClientException: Received 404 status code during operation: RETRIEVE_PAGES\n\tat io.atlassian.micros.instant.importers.NotionClientImpl.withRetry(NotionClientImpl.java:274)\n\tat io.atlassian.micros.instant.importers.NotionClientImpl.callNotionApi(NotionClientImpl.java:203)\n\tat io.atlassian.micros.instant.importers.NotionClientImpl.retrievePage(NotionClientImpl.java:97)
"message":"Failed to Retrieve Pages, error is Not Found, {\"object\":\"error\",\"status\":404,\"code\":\"object_not_found\",\"message\":\"Could not find page with ID: xxxx. Make sure the relevant pages and databases are shared with your integration.\"
Workaround
The only viable short-term option is to import only the content. Users should skip providing integration or access tokens and run a small import first to check if the results meet their needs.
Afterward, they can import the content in smaller chunks of 5-8 GB each and rearrange it as necessary.