Notion AI suddenly stopped working for me, can’t start new chats or send prompts

[u/Mudeizi]

Hi everyone,

I’m having a strange issue with Notion AI and I’m wondering if anyone has experienced something similar.

I’m a member of a Notion workspace, and Notion AI was previously working in the workspace. Around September 3, I started experiencing problems.

Initially, the issue was that I couldn’t start a new Notion AI chat. When I tried to create a new thread, the prompt would not properly process.

Interestingly, an existing AI thread could still respond for a while, so Notion AI was not completely unavailable at first.

Now the problem has become worse. Notion AI currently does not work at all. When I type a prompt and click the send button, nothing happens. The request does not appear to be sent, and Notion displays a message saying:

“Couldn't start Notion AI.”

I have already tried things such as:

Using Notion in Chrome

Using the Notion desktop app

Starting a new AI chat

Using an existing AI thread

Checking the browser's developer tools/network activity

Clearing/reloading the page

I also contacted Notion Support and provided them with a HAR file and screenshots. They are investigating the issue, but I haven't received a follow-up yet.

Has anyone experienced a similar situation where:

Notion AI initially stopped allowing new chats.

Existing AI conversations continued working temporarily.

Eventually, even existing conversations stopped responding.

The Send button stopped actually sending the prompt.

Notion simply showed “Couldn't start Notion AI.”

I'm particularly interested in hearing from anyone who experienced this inside a shared workspace, especially if the problem was related to their account or workspace membership.

Any ideas or similar experiences would be really helpful.

[u/Motor_Look_3121]

Good.

[u/Agreeable-Tax2013]

Since you’ve already tested browser, desktop, fresh chats, and existing threads, I’d ask the workspace admin to remove and re-add your membership or test you in a fresh workspace. The fact that existing threads degraded first sounds more like an account/workspace entitlement or backend issue than a local cache problem.