Notion Connector stops working mid-session — "no API access" error, model selector disappears in UI

Bug Reports
1

Description

During an active Pro session today (June 8, 2026), Perplexity was successfully creating Notion pages via the Notion connector. After some time, it suddenly stopped working and reported that it no longer has access to the Notion API. No changes were made to the connector or Notion workspace settings during the session.

Steps to Reproduce

  1. Open Perplexity (Pro plan)
  2. Enable the Notion connector in the chat
  3. Ask Perplexity to create a Notion page — it works initially
  4. Continue the session — at some point the connector stops functioning and returns an error about missing API access

Additional UI Issue

When the Notion connector is selected/active, the model selector disappears from the UI entirely, making it impossible to switch models manually.

Environment

  • Plan: Pro
  • Connector: Notion (official connector, not MCP/custom)
  • Notion workspace: active, no permission changes made
  • Perplexity not found in Notion's Connections settings (no disconnect option visible there either)

Expected Behavior

Connector maintains API access throughout the session and the model selector remains accessible when a connector is active.

Actual Behavior

Connector loses API access mid-session with no explanation. Model selector disappears from UI when connector is active.

2

Same problem, the connector works for the first fetch from Notion in a chat and thats it. After the first message it seems to be limited to generic web fetching, which cannot authenticate into a private Notion workspace.

3

To add to that, this began this week, at the same time that the connector call was forced to be per message through direct mention (@Notion) instead of simply enabling for the chat for the session (had to check the box again when leaving and reloading the chat, but not needed for consecutive queries). This makes the Notion connector basically unusable. Seems liek a bug introduced by that change.

4

I am seeing this behavior across all connectors on chrome and comet.

5

Update: Even though the part about having to select the connector for every message has been fixed where “@Notion” (for example) now appears automatically in the message as the first word when selected even for subsequent messages, the problem on fetching remains the same, only the first message will use the connector. Seems like a regression defect.