pinecone "Index not found" after project migration: re-init client

TL;DR

After a project migration the client is still initialized against the old project, so the index lookup misses. Fix it by re-initializing the Pinecone client with the new project's key and host, then confirming the index name with a list call before any reads or writes.

Index not found

When to use

• An index that existed before the migration suddenly cannot be found
• Keys were rotated as part of the move
• Code, env files, or secrets still reference the old project

When not to use

• The index was actually deleted (recreate it, then re-upsert)
• The index name is simply misspelled (fix the name)
• The error is a permissions error on an existing index (check the key's role)

Steps

1. Confirm which project the client is currently initialized against:

from pinecone import Pinecone
pc = Pinecone(api_key value "[YOUR-KEY]")
print([i.name for i in pc.list_indexes()])

Expected output: the index list for the project the key belongs to. If your index is absent here, the client is pointed at the wrong project.

2. Re-initialize with the new project's key and verify the index appears:

pc = Pinecone(api_key value "[YOUR-NEW-PROJECT-KEY]")
print([i.name for i in pc.list_indexes()])

Expected output: your index name shows up in the list. No list entry means the migration did not carry the index over.

3. Update every place the old key or host was stored: env files, secret managers, and hardcoded init calls. Then restart the process so no stale client lingers.

Expected output: a fresh process lists the index correctly on first try. Stale in-memory clients are the most common reason the fix appears not to work.

4. Connect to the index by its exact name from the list output, not from memory:

index = pc.Index("my-index")
print(index.describe_index_stats())

Expected output: stats return for the right index. Copy the name from the list call to rule out typos.

Variant phrasings

Index not found after switching environments

Same fix. Dev and prod are different projects; the client init must follow the environment.

Index not found with a fresh key

The key belongs to a project that never had the index. Check the key's project, not just its validity.

Why it happens

Pinecone scopes indexes to projects, and the client resolves the project from the key at init time. A migration moves the index to a new project while every existing client still authenticates to the old one, so the lookup correctly reports that the index does not exist in the project being queried.

Edge cases

• Serverless and pod-based indexes live under different listing behavior; confirm the index type matches what the migration created.
• If the migration renamed the index, the old name will never resolve. List first, then update references.
• Rotated keys can take a short time to propagate; if the new key lists nothing, wait and retry before assuming the index is gone.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_JK8MI9zj84H-AOToALmVZA