Since updating Cursor IDE to version 0.43.5, I’ve been running into an issue where document indexing consistently fails with an “Indexing failed” error. This has made it impossible to use the AI features that depend on document context. Everything was working fine before the update, so it seems to be a new issue. I’ve tried a few troubleshooting steps, but nothing has worked so far.
2 Likes
Which documentation are you trying to add?
I am adding Supabase docs and Travelport API docs.
https://support.travelport.com/webhelp/JSONAPIs/Airv11/Content/Air11/AirAPIs11.htm
1 Like
I even tried to only index some of the docs like the Supabase auth docs, but still it keeps on failing.
With 0.42.3 I cant index anything beyond few pages. 0.43.5 was a downgrade not an upgrade so I dropped back to 0.42.3. But had same issues with 0.43.5.
It’s simply broken and the devs either don’t test or ship broken crap on purpose.
2 Likes
Hello @deanrie, Do you have any solutions to this issue? I hope this does not get overlooked.
1 Like
Hey, yeah, I’ve shared this with our developers. We’re waiting for a fix.
Got it.
same here.
waiting for the update.
I got update version 0.43.6 update and indexing still failed on my machine even though I delete the link and paste to index again.
How about you guys?
I’m trying to index this “Introduction | Plugin API” but I’m having a hard time also. The task got in an “indexing fail” status, although by clicking on the “see pages” icon I can see that 410 pages have been indexed.
Am I missing something or it’s related to how those web pages are indexed?
Thanks!
It seems that documents are being indexed despite the “Indexing Failed” status. We are working to resolve this issue as soon as possible.
I try to index this page Troubleshooting guide | Gemini API | Google AI for Developers and others from the Google API, but I only get an error 
Same here, would be great to get an update as severly limiting ability to add new libraries information. Thanks!
Posting here to link to other feedback issue I commented on. Hoping to get some traction or at least some sort of update to this bug:
2 Likes
I also rely heavily on the Document Indexing feature. This feature is one of the only things separating Cursor from other AI-based code editors, and while this feature remains broken, there seems to be very little reason to continue paying for Cursor. Really hoping this issue gets resolved soon. 
2 Likes
In an effort to help the development team try to diagnose this issue for a faster fix, I am checking the Cursor Log files / Terminal Output.
Terminal > New Terminal > Open the dropdown, select Cursor Indexing & Retrieval
Here is the output from my log:
2024-12-15 09:57:16.846 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2024-12-15 09:57:16.846 [error] Error: Command failed: git config --get remote.origin.url
at genericNodeError (node:internal/errors:984:15)
at wrappedFn (node:internal/errors:538:14)
at ChildProcess.exithandler (node:child_process:423:12)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at Socket.<anonymous> (node:internal/child_process:457:11)
at Socket.emit (node:events:519:28)
at Pipe.<anonymous> (node:net:338:12)
2024-12-15 09:57:17.048 [error] NoWorkspaceUriError
And, also a screenshot here:
Version: 0.43.6
VSCode Version: 1.93.1
Commit: a846435528b4b760494a836f96f0739889253530
Date: 2024-12-06T05:11:55.168Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Not sure if this helps. Hopefully, we can politely raise some attention to this issue, since the Custom Doc Indexing is a core feature of the Cursor Editor. Hopefully, we can all raise awareness to the dev team and bring some much needed attention to resolving this issue, as this is affecting many users.
@moderators Sorry for tagging the entire moderator team - just trying to raise awareness about this issue with a core feature of the Cursor editor. Hopefully, this can be passed along to the dev team. Hope everyone is having a great weekend! 
We appreciate any/all help with this!
1 Like
I’m also trying to index this Drizzle ORM Documentation and it keeps failing.
Here’s the docs URL → https://orm.drizzle.team/docs/overview
Showing ‘Indexing Failed’ status. Please Fix ASAP. It is much needed because this is the only feature which outstands Cursor from all other AI Code Editors.
Thank You!
Looking forward for a fix to this Issue.
Best Wishes,
Sujay
hey! thanks for all the info on this! we’re deploying some fixes right now. trying to repro on our end to see if it’s properly fixed!
3 Likes
i can now index drizzle, can you verify on your end?
1 Like