When a document connector loses access, do not interpret every failed fetch as deletion or silently keep serving old protected content. Diagnose the source state and apply the defined access-failure policy.
Connector revocation changes authority
A connector may lose its service grant, resource permission, account membership, or required scope. Expired credentials and temporary outages can look similar but require different recovery.
For a proposed runbook, record the affected account and collection, safe failure category, last verified scope, pending sync work, and owner. Stop unsupported processing and determine what happens to already indexed material under the approved policy.
Do not broaden credentials automatically to make ingestion healthy. Access restoration needs the actual authorised owner and supported provider mechanism. A model-generated claim that a document is public does not override source denial.
Rehearse a fictional folder revocation
An organisation removes a connector’s access to one project folder. Other collections remain available. The pipeline should identify the affected scope and avoid a global blind rebuild or wholesale deletion based only on one access error.
The design may quarantine related derived content pending verification, perform current user checks, or use another explicitly approved policy. Its behaviour must be documented and tested rather than improvised during the incident.
| Failure condition | Recovery action |
|---|---|
| Credential expired | Supported credential repair |
| Resource access revoked | Authorised scope review |
| Temporary source outage | Bounded retry and freshness handling |
| Partial collection access | Scoped containment and reconciliation |
| Access restored | Verify current resources and removals before resume |
Use fictional resources and controlled error responses. Inspect active search results and caches during the incident, not only whether the connector eventually reconnects.
Reconcile after restoration
The source may have changed while access was unavailable. Use its supported checkpoint recovery or full reconciliation as needed, preserving removals and current permissions. Do not resume an old extraction job without checking whether its resource is still eligible.
Conservative containment can reduce availability, while continued stale serving can increase exposure or misinformation. The appropriate tradeoff depends on the actual source contract and risk. State it clearly and give unresolved content an accountable owner.
This recovery runbook is proposed. The voice integration case study describes related backend work without claiming this connector. Pair it with token-expiry recovery.
Connector access FAQ
Does access denied mean the document was deleted?
No. Preserve the distinction and use supported source evidence.
Can the connector request broader permission itself?
Only through the explicitly authorised organisational process, not as automatic error recovery.
What proves restoration?
Verify current scope, source state, pending work, active evidence, and the disposition of any stale or uncertain artifacts.