Pinecone Go SDK: client, retry policy, REST and gRPC

TL;DR

Set the retry policy at construction, not per call. Keep the SDK version current; the retry behavior and API versions move with it.

Steps

1. Set the retry policy at construction, not per call. Scattered retry logic drifts.
2. Read the key from the environment. Do not accept it as a CLI flag that ends up in process listings.
3. The same readiness rule applies: poll describe until ready after creating an index, even in Go.
4. Keep the SDK version current; the retry behavior and API versions move with it.

When to use

You are seeing this: ` pc, err := pinecone.NewClient(pinecone.NewClientParams{ ApiKey value os.Getenv("PINECONE\_API\_KEY"), RetryPolicy: pinecone.DefaultRetryPolicy(), }) DefaultRetryPolicy is 3 retries, 500ms base, 30s cap, 2x backoff with jitter. Use this skill when you run into "Pinecone Go SDK: client, retry policy, REST and gRPC".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Pinecone's error-handling guide documents the Go SDK RetryPolicy semantics: covers 429 and transient 5xx / gRPC UNAVAILABLE on REST and gRPC clients, never other 4xx. Verified against live docs 2026-09-26.