1. LandOffer
  2. Blog
  3. All articles
  4. Glean Cannot Find an Updated Work Document: Separate Access, Crawling, and Indexing

AI at Work

Glean Cannot Find an Updated Work Document: Separate Access, Crawling, and Indexing

Separate source access, connector retrieval, indexed revision and selected-user visibility. Includes a filled two-employee comparison and timestamped escalation ticket.

9 min readLandOffer team

When Glean cannot find an updated work document, check the original document with the affected person's own account before diagnosing search freshness. Then ask an authorized administrator to separate the document's last crawl, last index update, visibility, and that person's access in Glean. A colleague opening the source does not establish your access, and a recent crawl does not establish that the updated content is already searchable.

This LandOffer workplace guide reviews current Glean documentation checked on October 25, 2026. Its two-employee comparison and filled escalation ticket are fictional worked examples. All accounts, document IDs, timestamps, source checks, administrator findings, and search outcomes in those examples are invented. No Glean tenant, administrator console, connector, or internal document was accessed or changed while preparing this article.

Colleagues comparing an original updated reference with the separate intake and catalog records in an editorial archive workshop

Establish the exact source before changing the query

Record the canonical document URL, source application, and recognizable version marker. A title alone may identify an old copy, a shortcut, or a different team's document. Ask the owner which version should govern the current work and whether the change is saved or approved in the source.

Use your own authorized account to open that URL directly. Record whether you can see the expected updated section, not merely whether the page loads. Keep an access error separate from an old-content problem. If a colleague can open it but you cannot, take the access question to the source owner through the normal approval route. Do not ask them to make the file public or send a restricted copy to bypass access.

Capture one precise search attempt: query, time, selected source filters, and which result or version appeared. Try the agreed title or URL where appropriate, but do not keep rewriting prompts without preserving the original failure. Preserving that query and result lets the next reviewer repeat the same check instead of reconstructing the failure.

If a generated answer is the symptom, save the permitted citation or document link separately from the answer text. An answer sounding current is not evidence that it used the expected revision. Compare the cited source with the owner-confirmed version before relying on the answer for work.

Ask an administrator to separate four different signals

Glean's Access verification guide places Document lookup in the Admin console under Content management. It accepts a document URL or ID and can check a selected teammate. The displayed fields distinguish the last scan for changes, the last addition of changes to search, visibility, and selected-user access. Employees should request these findings from the authorized administrator rather than assume they have that console access.

Treat each signal as a separate observation. A document can be known to the system without the expected revision being confirmed. A result visible to one person does not establish another person's access. Record which person was selected during lookup; a screenshot without that context can answer the wrong question.

Do not translate a timestamp into a diagnosis by itself. A crawl before the source edit supports investigating freshness, but does not establish why retrieval has not caught up. An index timestamp after a crawl supports a different chronology, yet the actual result still needs to be checked against the expected version. Retain the lookup snapshot, owner-confirmed version marker, and affected user's search observation as separate evidence in the same report.

Glean's Crawl types documentation distinguishes full and incremental content work from identity-related retrieval. It also explains that an initial sync differs from later incremental work. These distinctions help frame the administrator's investigation; they do not tell an employee that a missing document requires a new full crawl.

A two-person diagnosis of the same updated document

The fictional source is a meeting-room equipment checklist, owned by Celia. Its canonical URL is https://work.example/docs/room-kit-42, a reserved example address, not a working company link. Celia saves revision 7 on October 26, 2026 at 09:10 UTC. Its distinguishing sentence says the spare presentation remote is kept in cabinet B rather than cabinet A. These are synthetic office details with no real operational authority.

Employees Rhea and Bruno both open that exact source URL using their own approved work identities. Rhea checks at 09:35 UTC and Bruno at 09:40; both see revision 7 and cabinet B. Bruno reports a recent membership change, but its timing and relevance to Glean remain unverified. It is a lead for the administrator, not the established cause.

At 10:00 UTC, the comparison record combines those employee observations with a fictional authorized administrator's lookup findings:

Evidence layer Rhea Bruno What the comparison supports
Direct source access Opens canonical URL, sees revision 7 at 09:35 Opens the same URL, sees revision 7 at 09:40 Both can currently reach the expected source revision; no request to broaden source sharing
Search observation Title query at 09:45 returns revision 6 with cabinet A Same title query and source filter at 09:50 returns no matching document Different search symptoms must be retained rather than merged into “Glean is down”
Lookup identity Administrator selects Rhea's work identity Administrator selects Bruno's work identity Findings are person-specific; nobody uses a colleague's session
Document identity and chronology Document ID EXAMPLE-DOC-42; last crawled 08:55; last indexed 09:00 Same document ID and document timestamps Both timestamps precede the 09:10 source edit; revision 7 ingestion is not established
Glean visibility and access Visible; selected-user access yes Visible; selected-user access no Bruno's Glean access needs a separate investigation even though source access succeeds
Missing information Applicable update path and crawl-health evidence not yet supplied Identity/group refresh state and explanation for access mismatch not supplied Neither API throttling nor group-sync delay has been proven

The initial decision is to keep two threads under one document report: freshness for Rhea, and the source-to-Glean access mismatch for Bruno. The source remains restricted as intended. Celia provides the authorized canonical reference for current work while the search investigation continues; that fallback does not extend access to anyone else.

The fictional administrator, Malik, owns connector and lookup review. Celia owns confirmation of source version and intended audience. Rhea owns the comparison report. Bruno is not asked to create a duplicate document, borrow credentials, or alter group membership until search begins working.

Use the applicable refresh path, not a generic waiting period

Glean's Connector refresh rates page explicitly describes defaults rather than deployment guarantees. Actual timing depends on configuration, source limits, scope, and crawl health. Event notification is not immediate search visibility, and permission changes may involve separate identity work. Its tables distinguish content, activity, and identity schedules; activity polling should not automatically be treated as a content-refresh deadline.

Ask the administrator which connector, indexed mode, and scope cover this particular document. “We use that app” is less specific than “this document is inside the indexed scope being checked.” Avoid transferring one connector's interval to another connector or treating a listed period as the end-to-end time from edit to a searchable result.

The access guide advises escalation when a document remains absent after the applicable expected updates or crawls and describes checking connector health before a targeted recrawl request. Let the administrator establish those conditions in the actual deployment. The fictional ticket below does not invent an applicable schedule or state that two expected cycles have already elapsed.

If the administrator reports the URL is not found, confirm the source URL and connector-specific format before concluding that content was deleted. Keep “not found in lookup” separate from an employee receiving no search results. Those observations come from different tools and may require different next checks.

An archive team keeps a completed intake check separate from the still-unresolved reader-access question at a catalog desk

A filled escalation ticket with an honest unknowns section

Rhea prepares this fictional ticket at 10:05 UTC. It contains enough evidence to route the investigation without including the entire source document. The identifiers and content below are synthetic; a real ticket should use the organization's approved support channel and permitted evidence.

Ticket field Completed example
Subject and impact Updated checklist revision not found consistently in Glean; two employees need the owner-confirmed cabinet location for an internal room-kit review. Source remains available to both; no complete work stoppage claimed
Canonical reference Source URL https://work.example/docs/room-kit-42; source identifier room-kit-42; Glean document ID EXAMPLE-DOC-42, supplied by authorized administrator
Expected revision Revision 7 saved by Celia on October 26, 2026 at 09:10 UTC; synthetic marker cabinet B. Revision 6 says cabinet A
Affected identities and attempts Rhea: direct source 09:35, search 09:45 returns revision 6. Bruno: direct source 09:40, search 09:50 absent. Same title query and source filter; identity details retained only in the approved internal ticket
Administrator findings Lookup snapshot 10:00 UTC: last crawled 08:55, indexed 09:00; document visible; Rhea access yes, Bruno no. Selected-user context recorded for each check
Known gaps Connector mode/scope, effective update path, crawl-health evidence, and group/identity refresh state not yet supplied. Recent membership change is unverified context, not root cause
Request and owners Malik: confirm applicable connector path, current content and identity status, and next diagnostic step. Celia: confirm intended audience and revision. Request targeted support investigation if the applicable conditions warrant it; no blanket recrawl requested
Interim work and privacy Use owner-confirmed source through existing permissions. No public sharing, duplicate upload, access expansion, API token, or full-document attachment proposed

An escalation should identify the unresolved checks for the next responsible owner. Here that question is whether revision 7 has passed the applicable retrieval and indexing work, plus why Bruno's selected-user access differs from current source access. “Fix search urgently” would conceal the distinction and make later verification harder.

Read the follow-up without declaring both problems fixed

In the fictional follow-up, Malik supplies another lookup snapshot at 11:00 UTC: last crawled 10:40, last indexed still 09:00. Rhea's source remains revision 7. The later crawl timestamp is new evidence, but the recorded index time still precedes the edit. Rhea leaves freshness open rather than replacing the report with “crawl complete, resolved.”

At 11:30 UTC, the fictional lookup shows last indexed 11:15. Rhea's repeat search now returns revision 7 and the cabinet B marker. The report records that specific successful comparison for Rhea. Bruno's selected-user access still says no, and his repeated search remains absent; the mismatch is not resolved by Rhea's result.

Rhea adds an 11:35 UTC ticket update linking both snapshots and keeps Bruno's access investigation assigned to Malik. No cause is established for that remaining discrepancy, and no restoration date is promised. Malik's next requested update is the identity/permission investigation and a repeat lookup and search for Bruno after any authorized correction. This sequence is a worked example, not a tested Glean recovery timeline or performance benchmark.

Before closing your own report, record the affected person's repeat search and expected-version comparison, preserve the lookup timestamps, and leave any remaining access problem assigned to its owner. Send only approved evidence through the appropriate internal route. A newer timestamp or one colleague's success should not silently close someone else's unresolved case. More workplace guides are available through LandOffer.

Sources and Further Reading