Pinecone diagnosis: query-by-id behaves unexpectedly

TL;DR: Symptom: querying by vector id returns odd results or fails. Query-by-id compares one stored vector against the index; it is not a fetch, and it has its own limits. Confirm it 1. Run fetch on the id: if fetch works, the record exists and the issue is query semantics.

The fix

1. Run fetch on the id: if fetch works, the record exists and the issue is query semantics.
2. Check the namespace on the query call; query-by-id still scopes to a namespace.
3. Check whether a filter is excluding the expected neighbors.
4. For point lookups use fetch, not query(id=...).
5. For find-similar-to-this-record, keep query(id=...) but set namespace, top_k, and filter deliberately.
6. If you need the vector values back too, pass include_values=True; matches do not include values by default.

When to use this

• This covers exactly what the title says: Pinecone diagnosis.
• You are setting this up for the first time, or auditing an existing setup.
• You want the key gotchas in one place before you start.

When not to use this

• You are doing a different workflow with Pinecone; these steps are specific to the title above.
• You need the full reference docs; this is the short path, not the manual.

Compatibility

• Not pinned to a specific version; follows current Pinecone behavior.

Pinecone's querying-by-id limitations troubleshooting page and the query guide define the find-similar semantics and its limits versus fetch. Verified against live docs 2026-09-26.