Should DEADLINE_EXCEEDED be retried for non-idempotent Google Cloud client library calls?
Google Cloud client libraries built on gRPC expose layered timeout controls: a total timeout, a per-RPC attempt deadline, and retry settings that can be overridden per call. By default, idempotent RPCs are typically retried on codes such as UNAVAILABLE and DEADLINE_EXCEEDED, while non-idempotent operations such as resource creation are often excluded from de
google