Notion and ChatGPT Connection Errors

Notion Authorization Is Invalid or Expired

Symptoms can include an invalid-token message, a 401 response, or a destination list that no longer loads.

1. Open the extension popup.
2. Click Connected to Notion to start authorization again.
3. Select the workspace and pages the extension should access.
4. Return to the popup or Batch Sync page.
5. Refresh the destination list and select the destination again.

A Notion Destination Is Missing

The current extension lists writable Notion data sources. A Notion database with multiple data sources may appear as multiple choices.

If a destination does not appear:

1. Confirm it still exists and you can edit it in Notion.
2. Update Notion authorization and include the page that contains it.
3. Click the refresh icon beside the destination selector.
4. If you cloned a template after authorization, authorize the new clone.

”Could Not Find Page” or 404

The saved destination may have been deleted, moved, or removed from the integration’s access.

• Open Notion and confirm the destination still exists.
• Re-authorize the correct page.
• Select a different destination if the old one was deleted.

For repeat conversation exports, a previously created page that is in Notion Trash is treated as inactive. The extension creates a new active page instead of updating or restoring the trashed page.

File Upload Permission Error

Supported ChatGPT images and files are uploaded to Notion. If Notion returns a 403 or the extension says file-upload capability is missing:

1. Reconnect Notion.
2. Review the requested capabilities.
3. Allow file uploads.
4. Retry with the same destination and export settings.

If only one attachment fails, the extension continues exporting the conversation and adds a warning. Notion workspace file-size limits and unavailable ChatGPT download URLs can also cause attachment warnings.

ChatGPT Page Required

Open chatgpt.com in a browser tab, then reopen the popup or return to Batch Sync.

If ChatGPT is already open but the extension cannot connect, refresh that tab. See Why do I need to refresh the ChatGPT page?.

ChatGPT Rate Limit (429)

A ChatGPT 429 error is different from a Notion write limit. Batch Sync stops source requests to avoid making the limit worse while preserving confirmed work.

• Wait before retrying.
• Increase ChatGPT request pacing to a range such as 2–3 seconds.
• Keep completed-record skipping enabled.
• Retry with the same destination and settings.

See the 429 recovery guide.

Notion Request or Validation Error

The current writer automatically:

• Limits rich text, arrays, nesting, block counts, and request byte size
• Sends safe batches through a Notion request limiter
• Uses the Notion SDK retry policy
• Splits rejected payloads and retries smaller requests

If an export still fails, retry once without changing the destination or export settings. A partial export may resume from its last confirmed batch.

Contact Support

Send [email protected]:

• A screenshot of the visible error
• Whether it happened in Popup, Custom Export, Batch Sync, or Auto Sync
• The source type: Chat Page, Project, Group Chat, or Archived Chat
• Whether the conversation contained images or files
• The approximate number of messages or conversations

Do not send Notion access tokens, ChatGPT session tokens, or other credentials.