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 error

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.
7. This covers exactly what the title says: Pinecone diagnosis.
8. You are setting this up for the first time, or auditing an existing setup.
9. You want the key gotchas in one place before you start.
10. You are doing a different workflow with Pinecone; these steps are specific to the title above.
11. You need the full reference docs; this is the short path, not the manual.
12. Not pinned to a specific version; follows current Pinecone behavior.

When to use this

• You are seeing this exact error message; match the block above, not just part of it.
• The failing call matches the scenario in the title: Pinecone diagnosis.
• You want the fastest verified fix before digging through logs.

When not to use this

• Your error text differs from the block above; close cousins often have different causes.
• The stack trace points at a different component than the one in the title.
• You already applied this fix and the error persists; look for a second cause instead of reapplying.

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.