# Document Indexing Fails After Latest 0.45.11 Update

**URL:** <https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760>\
**Category:** Bug Reports\
**Created:** [February 13, 2025, 5:42pm UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760 "2025-02-13T17:42:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sujayxaradhya](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sujayxaradhya/32/16026_2.png) [@sujayxaradhya](https://forum.cursor.com/u/sujayxaradhya)\
**Post date:** [February 13, 2025, 5:42pm UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/1 "2025-02-13T17:42:10Z")

</div>

I can’t able to index Better Auth Docs, Tanstack Router Docs, Brevo Docs. Below are the links to the mentioned docs:

1. Better Auth Docs - [Introduction | Better Auth](https://www.better-auth.com/docs/introduction)
2. Tanstack Router Docs - [Overview | TanStack Router React Docs](https://tanstack.com/router/latest/docs/framework/react/overview)
3. Brevo Docs - [https://developers.brevo.com/](https://developers.brevo.com/)

**Sometimes, indexing is successfully done with missing out on some pages. There’s like 1 or less than 50 pages are being indexed but not full documentation. Sometimes indexing is being failed automatically. There are so many issues in indexing documentations.** Please fix this ASAP!

Thank You!

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 14, 2025, 4:53am UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/2 "2025-02-14T04:53:04Z")

</div>

Hey, thanks for the report, we’re already working on fixing it.

---

<div class="post-metadata">

**Author:** ![sujayxaradhya](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sujayxaradhya/32/16026_2.png) [@sujayxaradhya](https://forum.cursor.com/u/sujayxaradhya)\
**Post date:** [February 14, 2025, 8:58am UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/3 "2025-02-14T08:58:12Z")

</div>

Thank you for your response.

Will that be fixed in the upcoming update or you guys will fix it on the go? When we can expect this problem will be fixed?

I’m looking forward to your reply.

Thank You!

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 14, 2025, 11:49am UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/4 "2025-02-14T11:49:38Z")

</div>

I can’t say exactly when this will be fixed, but yes, it will be in one of the future updates.

---

<div class="post-metadata">

**Author:** ![sujayxaradhya](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sujayxaradhya/32/16026_2.png) [@sujayxaradhya](https://forum.cursor.com/u/sujayxaradhya)\
**Post date:** [February 14, 2025, 2:58pm UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/5 "2025-02-14T14:58:03Z")

</div>

Okay, we will be waiting!

---

<div class="post-metadata">

**Author:** ![foxgrover](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/foxgrover/32/26762_2.png) [@foxgrover](https://forum.cursor.com/u/foxgrover)\
**Post date:** [February 14, 2025, 4:33pm UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/6 "2025-02-14T16:33:58Z")

</div>

+1 this is a killer feature that’d be awesome to see fixed

---

<div class="post-metadata">

**Author:** ![florentin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/florentin/32/29494_2.png) [@florentin](https://forum.cursor.com/u/florentin)\
**Post date:** [February 25, 2025, 10:41am UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/7 "2025-02-25T10:41:36Z")

</div>

Can’t index [Welcome to Expression — Expression](https://expression.readthedocs.io/en/latest/intro.html) either. It shows “Indexed 0 pages” in Cursor Darwin arm64:  
Version: 0.46.4  
VSCode Version: 1.96.2  
Commit: db71624816f6d52f6e54f47c37cdc7df23e22620  
Date: 2025-02-25T07:28:07.050Z  
Electron: 32.2.6  
Chromium: 128.0.6613.186  
Node.js: 20.18.1  
V8: 12.8.374.38-electron.0  
OS: Darwin arm64 24.3.0

---

<div class="post-metadata">

**Author:** ![florentin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/florentin/32/29494_2.png) [@florentin](https://forum.cursor.com/u/florentin)\
**Post date:** [March 19, 2025, 10:36am UTC](https://forum.cursor.com/t/document-indexing-fails-after-latest-0-45-11-update/50760/8 "2025-03-19T10:36:20Z")

</div>

Maybe this helps, in Cursor 0.47.8 I was able to add the `stable docs` `https://expression.readthedocs.io/en/stable/intro.html`.

The `latest` docs from `https://expression.readthedocs.io/en/latest/intro.html` still don’t work.

I was also able to server the docs for Expression on localhost, use ngrok to expose them online and ask Cursor to index the docs.
