Gemini Notebook Not Working? Check Imports and Evidence

If Gemini Notebook is not working, check account access first, then test whether the source imported correctly and whether your question can be answered from it. A notebook that opens successfully can still contain an inaccessible source or give an answer that needs correction.

Google’s current help center↗ (opens in a new tab) calls the product Gemini Notebook; older references may use NotebookLM. Keep the project’s reference links and approved findings in a separate work record such as fenbs, so troubleshooting does not erase what you have already established.

What is the quickest way to locate the failure?

1. Write down the failing action: opening the service, opening a shared notebook, adding a source, asking a question, or generating an output.
2. Confirm the signed-in Google account. Open the original source using that same identity and check that you can read it.
3. Try a small source you are authorized to use with a distinctive fact you can verify. Ask a direct question about that fact.
4. Compare the imported source with its original, then repeat the same question after changing one condition. Preserve useful notes before deleting anything.

Use the browser experience for this comparison if a mobile control is missing. Google’s source and chat guides flag mobile differences, so an absent button does not necessarily mean the source itself is broken. Our Gemini Notebook guide covers the general workflow; the checks here focus on failures.

Why can you not open the service or a shared notebook?

Start with the account shown in your profile menu, especially if you switch between personal and work identities. A sharing invitation sent to one account does not establish access for another. Ask the notebook owner to confirm the intended address before making a second copy of the research.

Google’s work and school account guidance↗ (opens in a new tab) explains that availability, features, and data handling depend on the account’s license. Ask your administrator to check the services and access assigned to your account. Use Google’s current documentation for allowances rather than treating a remembered limit as universal.

For a page that fails to load, preserve unsent text, reload, and compare with an updated browser in another window. If only one browser profile fails, check its signed-in identity and extensions. If several authorized users see the same error, give support that common failure rather than changing everybody’s files independently.

Why does adding a source fail?

Check the source type, its permissions, and its actual readable content. A working link in your browser is not proof that a notebook importer can read everything on that page. Google’s source import guide↗ (opens in a new tab) lists supported formats, current limits, and restrictions for web pages, Drive files, video, and audio.

For a web source, check whether the material is ordinary page text, behind a paywall, inside a video, or on another linked page. Google describes web imports as extracting the specified page’s text, without pulling in nested pages or embedded videos. Supply the relevant supported source directly rather than assuming the whole site was imported.

For a PDF, confirm you are allowed to use it and that its protection settings permit import. Try opening and searching the original. If you prepare a smaller readable version, preserve headings, table labels, and qualifications; removing the footnote that changes a result can produce a convincing but incorrect answer.

For video or audio, check Google’s specific requirements before retrying. Public video availability, captions, speech, language support, and recording quality can affect import. A useful test is to compare a short known passage with the imported text rather than judging success by the source title alone.

Keep the authoritative URL and the failed import check in fenbs Links and listings. That gives the next session a route back to the original instead of leaving a detached summary as its only evidence.

Why is an existing source stale or inaccessible?

Do not assume all source types update in the same way. Google’s source guide describes automatic syncing for supported Drive imports and a manual sync control when needed. It also says losing access to a Drive original, or its deletion, can make the notebook source inaccessible. Repeatedly asking the same question will not restore that permission.

Open the original and the notebook source side by side. Check a sentence that changed recently, along with the document’s title and version. If the original opens but the imported content differs, use the applicable sync or replacement workflow and repeat the check before relying on a new summary.

Keep local uploads and exported copies under your own version discipline. Label which copy supports a finding, and treat a changed original as a reason to recheck that finding. A notebook summary is evidence of what the model produced, not proof that the underlying source remains current.

Why does an answer lack citations or miss the evidence?

Select the relevant sources and ask a question tied to a named document or section. Google’s chat instructions↗ (opens in a new tab) explain how source selection and citations work. Open the cited passage and read its surrounding context; a citation marker alone does not prove the answer represents the document fairly.

Say a research notebook contains interview notes and a final approval memo. Ask what the memo approves, then separately ask what the interviews suggest. If the response merges them, narrow the selected sources and require it to identify uncertainty. Suggestions from research should not quietly become a client’s approved instruction.

Google’s troubleshooting FAQ↗ (opens in a new tab) notes that a very short source may be used without individual text citations. Check the source itself in that case. When the available material does not answer your question, supply the missing evidence or accept that the answer remains unknown.

If the error concerns a connected source in ChatGPT instead, use our ChatGPT connector troubleshooting guide. Permission controls and source behavior differ between products, even when both start from the same document.

How to do this with fenbs

1. Create a free account, free for one person with no credit card, and add the project to your kanban board.
2. Add the source locations to Links and listings. Save only the background your project needs in context notes, with enough detail to find the original.
3. Record human approvals in Decisions and rules. Create a task for each unresolved source or answer check and record what succeeded or failed.
4. Use the integration guides to connect a supported assistant over MCP, a standard way for an AI app to use an outside tool. Ask it to read the project context before working and save Where we left off before stopping.

fenbs does not import notebook sources automatically or repair Google account access. It is not a replacement for a source-analysis notebook when that is all you need. It helps keep the project’s conclusions and next-session handoff available after the research session ends.

If your notebook is Microsoft’s product, see Copilot Notebooks troubleshooting. For the wider practice of choosing and checking an assistant’s working information, visit our context engineering hub.