# Coverage and freshness

Tell which account, records, time range, and current state a connector result actually covers.

Choose the route according to the question. “What is on my calendar now?” needs a current provider read. “What did we decide last month?” may be answered from collected records. A connected source can support one route without supporting the other.

## Choose live access or collected context

| Route | Use it when | Information retained |
| --- | --- | --- |
| Provider Action or local `connector.read` | You need a current item or a focused operation. | Current local Action payloads are returned to the caller without automatically adding them to the shared search collection. |
| Local Cloud `indra.read` | A remote client needs a selected source page and subsequent SQL search. | Only the returned page is cached for search. |
| Full or incremental sync | You need supported history available for later cross-source queries. | Supported records are collected in the Vault. |
| `indra.search` | You need information already in the Vault. | Reads the existing collection; it does not fetch missing provider data. |

This explains a common apparent contradiction: a live read can succeed while a local SQL search returns no rows. Check which route was used before reconnecting or repeating an import.

## Read one bounded page

Inspect the source's available operations first. Where the shared read operation is supported, the terminal form is:

```sh
indra --root "/absolute/path/to/your/Vault" action --json '{"name":"connector.read","params":{"source":"gmail","request":{"limit":5}}}'
```

The corresponding MCP call is `indra.action` with the same JSON object. The optional request supports a bounded `limit` and, where the source supports them, `query`, `since`, and `until`. A provider can report unsupported filters or omissions; do not assume every source implements the same search semantics.

For a provider-specific method, inspect its live schema and use [Run an action](/docs/vision/tools/actions). Do not invent a cursor field in the shared read request. Follow only a continuation actually returned and documented by that method.

## Establish the useful boundary

Before treating a result as complete, answer:

- Which account, workspace, profile, folder, or library was used?
- Which resource types and dates were requested?
- Was this one page, a selected item, a full pass, or a retained search?
- Did the result report a limit, omitted body, unsupported item, or unfinished cursor?
- Is its observation recent enough for the question?

A calendar-only route does not establish mail coverage. An own-posts route does not cover an entire social feed. Metadata does not prove a document's body was read.

## Handle an empty result

A successful empty response means the operation found no items within its actual scope. It does not prove the whole account is empty or the event never happened.

For an empty Vault search, check the source inventory and collection state, then try a small live read if supported. For an empty live read, check account and filters before widening the request. Keep successful emptiness separate from `unauthenticated`, `unavailable`, or a provider error.

## Explain partial coverage

Useful reporting is specific:

> I checked the selected work calendar for Monday through Friday. The read returned three events. I did not inspect other calendars.

> I found two retained planning documents. The latest Drive collection is incomplete, so this does not establish that they are the newest versions.

For large historical work, follow [Sync your sources](/docs/vision/connectors/sync). For a current document, use its exact provider identity and read the latest version directly.
