# Indexing Failed for \*some\* (?) sites: Error when trying to chat "Non-turbopuffer vector databases are no longer supported"

**URL:** <https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680>\
**Category:** Bug Reports\
**Created:** [January 2, 2025, 1:48pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680 "2025-01-02T13:48:16Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jldb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jldb/32/1352_2.png) [@jldb](https://forum.cursor.com/u/jldb)\
**Post date:** [January 2, 2025, 1:48pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/1 "2025-01-02T13:48:16Z")

</div>

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.

### Describe the Bug

I am trying to index a site ([Cloudflare Provider | Pulumi Registry](https://www.pulumi.com/registry/packages/cloudflare/)) and every time it gets to ~190 pages and then just returns “Indexing failed”. Retrying a number of times does not resolve the issue.

When then trying to chat with what docs it does have in the index, it fails with “Non-turbopuffer vector databases are no longer supported”

### Steps to Reproduce

Version 0.44.9 - Mac (Apple Silicon)

1. Index the website mentioned above: [Cloudflare Provider | Pulumi Registry](https://www.pulumi.com/registry/packages/cloudflare/)
2. Try and chat with the docs that were indexed

### Expected Behavior

Docs are indexed and can be used in chat/composer.

### Screenshots / Screen Recordings

 ![Screenshot 2025-01-02 at 14.46.58.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/9/a97bc20db5248704389393109ccf6fa96074767b.png)

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version 0.44.9  
Request ID: e6c15d4c-16d7-48f7-8019-3605629e94d8

### Additional Information

No other additional information I can think of. The only thing I notice is I _think_ it’s downloading some existing embeddings from somewhere when I first add the site, and that’s what’s being submitted because the index fails.

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![shaunchurch](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/shaunchurch/32/18235_2.png) [@shaunchurch](https://forum.cursor.com/u/shaunchurch)\
**Post date:** [January 2, 2025, 2:21pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/2 "2025-01-02T14:21:38Z")

</div>

fwiw I’m seeing the same thing trying to use docs in composer today.

---

<div class="post-metadata">

**Author:** ![bezerra-lucas](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bezerra-lucas/32/18242_2.png) [@bezerra-lucas](https://forum.cursor.com/u/bezerra-lucas)\
**Post date:** [January 2, 2025, 2:38pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/3 "2025-01-02T14:38:57Z")

</div>

same error here, it seems to happens with all “@docs”  
also, the agent stopped doing vector searches on the codebase

---

<div class="post-metadata">

**Author:** ![nyxb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/nyxb/32/11066_2.png) [@nyxb](https://forum.cursor.com/u/nyxb)\
**Post date:** [January 2, 2025, 2:50pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/4 "2025-01-02T14:50:55Z")

</div>

same And it’s really annoying when you pay for something and it just doesn’t work, and also no one anywhere responds to it.

> [@Why can't I use docs with agent mode in Cursor 0.44?](https://forum.cursor.com/t/why-cant-i-use-docs-with-agent-mode-in-cursor-0-44/38588/10):
>
> I’m in the same situation. Does anyone know the solution?

> [@Error: Request Type Deprecated when using @docs in Composer Agent Mode](https://forum.cursor.com/t/error-request-type-deprecated-when-using-docs-in-composer-agent-mode/38610/3):
>
> Yup me too…

/t/critical-error-request-type-deprecated-when-using-docs-in-normal-chat-and-in-composer-normal-and-agent-mode-both/38686

---

<div class="post-metadata">

**Author:** ![daneroo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/daneroo/32/8187_2.png) [@daneroo](https://forum.cursor.com/u/daneroo)\
**Post date:** [January 2, 2025, 2:54pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/5 "2025-01-02T14:54:56Z")

</div>

> [@jldb](#):
>
> rks, but with this issue

I have the same error, for any @Docs

---

<div class="post-metadata">

**Author:** ![rikard](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rikard/32/18245_2.png) [@rikard](https://forum.cursor.com/u/rikard)\
**Post date:** [January 2, 2025, 2:55pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/6 "2025-01-02T14:55:18Z")

</div>

This worked just a couple of hours ago so it seems to be something temporary

---

<div class="post-metadata">

**Author:** ![maxondria](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@maxondria](https://forum.cursor.com/u/maxondria)\
**Post date:** [January 2, 2025, 3:13pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/7 "2025-01-02T15:13:46Z")

</div>

I am getting the same issue in chat! Everytime I try to attach docs

---

<div class="post-metadata">

**Author:** ![fradal64](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/fradal64/32/18246_2.png) [@fradal64](https://forum.cursor.com/u/fradal64)\
**Post date:** [January 2, 2025, 3:18pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/8 "2025-01-02T15:18:53Z")

</div>

Same problem here. Please fix it!!

---

<div class="post-metadata">

**Author:** ![jldb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jldb/32/1352_2.png) [@jldb](https://forum.cursor.com/u/jldb)\
**Post date:** [January 2, 2025, 3:43pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/9 "2025-01-02T15:43:32Z")

</div>

A shame to see this keeps reoccuring; here’s another thread I raised about all the same things back in June:

> [@Please be more responsive on the forum](https://forum.cursor.com/t/please-be-more-responsive-on-the-forum/6005):
>
> This is more of a general question, so apologies if it’s in the wrong place. I’ve been a big fan of Cursor for almost a year now; but in the last ~3 months the quality and usefulness that’s decreased such a phenomenal extend… almost no AI features work now (interpreter, Copilot++, most of the chat context/docs crawling not working properly/consistently/debuggable… it’s really starting to become quite the slog. Multiple requests for help in the forum just go unanswered - have the team moved to …

The price issues are particularly stinging, because despite the price of all the LLMs coming down, the “pro” requests are still fixed at their 500 calls, and even when a call fails inside of Cursor, you still get billed, anyway ¯\_(ツ)\_/¯

It’s easy to slam AI IDEs - people are trying to do something remarkable and something we never had before. That being said, the constant issues and bugs which sometimes block critical AI features working for “random periods of time” with almost no communication (and certainly no refunds or service credits for the continuous problems) could be solved with better transparency and communication, still.

I hope this is resolved soon.

---

<div class="post-metadata">

**Author:** ![victorcosta](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@victorcosta](https://forum.cursor.com/u/victorcosta)\
**Post date:** [January 2, 2025, 3:58pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/10 "2025-01-02T15:58:09Z")

</div>

same issue here, but just with this doc [Introduction to Haystack 2.x](https://docs.haystack.deepset.ai/docs/intro)

---

<div class="post-metadata">

**Author:** ![socrates8300](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/socrates8300/32/18251_2.png) [@socrates8300](https://forum.cursor.com/u/socrates8300)\
**Post date:** [January 2, 2025, 4:00pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/11 "2025-01-02T16:00:54Z")

</div>

Yes, I can’t use my docs/vector db at all. My work has slow to a crawl today.

---

<div class="post-metadata">

**Author:** ![Ibrahima-prog](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ibrahima-prog/32/11487_2.png) [@Ibrahima-prog](https://forum.cursor.com/u/Ibrahima-prog)\
**Post date:** [January 2, 2025, 5:33pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/13 "2025-01-02T17:33:13Z")

</div>

i got the same issue with `[Laravel Livewire](https://livewire.laravel.com/docs/quickstart)` docs

---

<div class="post-metadata">

**Author:** ![sw2025](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@sw2025](https://forum.cursor.com/u/sw2025)\
**Post date:** [January 2, 2025, 5:45pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/14 "2025-01-02T17:45:05Z")

</div>

Same here for the past hour

---

<div class="post-metadata">

**Author:** ![i-like-cookie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/i-like-cookie/32/18265_2.png) [@i-like-cookie](https://forum.cursor.com/u/i-like-cookie)\
**Post date:** [January 2, 2025, 5:45pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/15 "2025-01-02T17:45:13Z")

</div>

same error here

---

<div class="post-metadata">

**Author:** ![victorcosta](https://avatars.discourse-cdn.com/v4/letter/v/f4b2a3/32.png) [@victorcosta](https://forum.cursor.com/u/victorcosta)\
**Post date:** [January 2, 2025, 5:48pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/16 "2025-01-02T17:48:17Z")

</div>

same here with [Introduction to Haystack 2.x](https://docs.haystack.deepset.ai/docs) doc

---

<div class="post-metadata">

**Author:** ![paulba71](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/paulba71/32/18214_2.png) [@paulba71](https://forum.cursor.com/u/paulba71)\
**Post date:** [January 2, 2025, 5:53pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/17 "2025-01-02T17:53:05Z")

</div>

Yup me too. Not been working all day for me…

---

<div class="post-metadata">

**Author:** ![nyxb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/nyxb/32/11066_2.png) [@nyxb](https://forum.cursor.com/u/nyxb)\
**Post date:** [January 2, 2025, 5:57pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/18 "2025-01-02T17:57:37Z")

</div>

Well, I’m not sure if that’s the solution, but I deleted the index and all docs once. Then reset everything again and currently it works. However, I can’t say yet whether it will stay this way.

---

<div class="post-metadata">

**Author:** ![alirazacodes](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@alirazacodes](https://forum.cursor.com/u/alirazacodes)\
**Post date:** [January 2, 2025, 6:54pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/19 "2025-01-02T18:54:50Z")

</div>

Hey it works now, I didn’t deleted anything, I guess the error was temp.

---

<div class="post-metadata">

**Author:** ![jldb](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jldb/32/1352_2.png) [@jldb](https://forum.cursor.com/u/jldb)\
**Post date:** [January 3, 2025, 3:18pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/20 "2025-01-03T15:18:20Z")

</div>

To me it looks like it’s not working properly, or at least I can’t get it to work properly still, although don’t know how to debug it any further than the following:

1. Have a failed doc indexing task (or appears to be any task?), click “reindex”
2. Reindex immediately reports “Indexed”

Result:

The documents do not appear to be indexed.

I checked all the various “Outputs” I could for Cursor, but couldn’t find anything. Do please let me know if there’s any further way I can help.

---

<div class="post-metadata">

**Author:** ![alirazacodes](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@alirazacodes](https://forum.cursor.com/u/alirazacodes)\
**Post date:** [January 3, 2025, 6:44pm UTC](https://forum.cursor.com/t/indexing-failed-for-some-sites-error-when-trying-to-chat-non-turbopuffer-vector-databases-are-no-longer-supported/38680/21 "2025-01-03T18:44:42Z")

</div>

Yeah that’s right, its not crawling through the docs anymore, its busted… don’t know when it will be fixed… It only goes to the first introduction page and then that’s it, no further @curosr
