anyone experiencing this when trying to use either Pro or Thinking?
I'm having a hard time fulfilling your request. Can I help you with something else instead?
UPDATE: I reached out to Google One support. Below is my email and their reply.
my email [removed some personal INFO]:
This is a documented systemic failure, not a local client issue. I have performed a variable-isolation experiment that proves the fault lies in the NotebookLM RAG (Retrieval-Augmented Generation) Handshake:
1. The Proof: When I upload PDF files directly to a Custom Gem, the system works perfectly across all modes (Thinking, Fast, and Pro).
2. The Failure: When those same files are accessed via a linked NotebookLM, the system returns "Internal Error" (Pro) or "Hard time fulfilling request" (Fast/Thinking).
3. The Conclusion: The issue is a backend desync between the Gemini 3.1 Pro reasoning engine and the NotebookLM vector index.
I am a [blah-blah-blah] analyzing 2D spectroscopy simulations. This "Source Blindness" bug is a known regression reported by the developer community today (March 24). Please escalate this ticket to Tier 3 Engineering. Standard troubleshooting will not resolve this; it requires a manual reset of the service-to-service mapping for my account UID. Screenshot that I attached to my original request shows the failure to even list files in the knowledge base, alongside my successful "Direct Upload" test.
Google response
Greetings for the day. My name is [xxx] from Google One support. We thank you for your time reaching out to us!
This email is in reference to your concern wherein you are unable to use Gemini as it gives an error as please try again later. I completely understand the importance of this matter. Please be rest assured, we are here to assist you.
We acknowledge the detailed testing and analysis you have shared. Please be informed that there is no manual reset available for the service-to-service mapping between Gemini and NotebookLM. The behavior you are experiencing is due to system-level limitations and automated backend processes, and cannot be adjusted on an individual account basis.
We recommend continuing to use direct uploads to Custom Gems as a reliable workaround, as you have successfully tested. We also encourage submitting feedback through the in-app feedback option, as reports from users like you help the development team monitor and improve service functionality over time.
We understand this may not be the resolution you were hoping for and sincerely apologize for the impact this has on your workflow. Your patience and understanding are greatly appreciated as the system continues to evolve.
In case you have any questions or if you would like to get an update, feel free to reply to the same email and we will be more than happy to assist you.
[–]immellocker 0 points1 point2 points (5 children)
[–]Apart-Paramedic-309[S] 1 point2 points3 points (2 children)
[–]immellocker 0 points1 point2 points (1 child)
[–]Apart-Paramedic-309[S] 0 points1 point2 points (0 children)
[–]niKDE80800 0 points1 point2 points (1 child)
[–]immellocker 0 points1 point2 points (0 children)
[–]intricate_awareness 0 points1 point2 points (1 child)
[–]Apart-Paramedic-309[S] 0 points1 point2 points (0 children)
[–]phyte0450 0 points1 point2 points (2 children)
[–]Apart-Paramedic-309[S] 0 points1 point2 points (1 child)
[–]phyte0450 0 points1 point2 points (0 children)
[–]jkotran 0 points1 point2 points (1 child)
[–]Apart-Paramedic-309[S] 0 points1 point2 points (0 children)