Reference documentation and code samples for the Google API Common Protos Client class RetryInfo.
Describes when the clients can retry a failed request. Clients could ignore
the recommendation here or retry when this information is missing from error
responses.
It's always recommended that clients should use exponential backoff when
retrying.
Clients should wait until retry_delay amount of time has passed since
receiving the error response before retrying. If retrying requests also
fail, clients should use an exponential backoff scheme to gradually increase
the delay between retries based on retry_delay, until either a maximum
number of retries have been reached or a maximum retry delay cap has been
reached.
Generated from protobuf message google.rpc.RetryInfo
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Google API Common Protos Client - Class RetryInfo (4.12.3)\n\nVersion latestkeyboard_arrow_down\n\n- [4.12.3 (latest)](/php/docs/reference/common-protos/latest/Rpc.RetryInfo)\n- [4.12.2](/php/docs/reference/common-protos/4.12.2/Rpc.RetryInfo)\n- [4.11.0](/php/docs/reference/common-protos/4.11.0/Rpc.RetryInfo)\n- [4.10.0](/php/docs/reference/common-protos/4.10.0/Rpc.RetryInfo)\n- [4.9.0](/php/docs/reference/common-protos/4.9.0/Rpc.RetryInfo)\n- [4.8.3](/php/docs/reference/common-protos/4.8.3/Rpc.RetryInfo) \nReference documentation and code samples for the Google API Common Protos Client class RetryInfo.\n\nDescribes when the clients can retry a failed request. Clients could ignore\nthe recommendation here or retry when this information is missing from error\nresponses.\n\nIt's always recommended that clients should use exponential backoff when\nretrying.\nClients should wait until `retry_delay` amount of time has passed since\nreceiving the error response before retrying. If retrying requests also\nfail, clients should use an exponential backoff scheme to gradually increase\nthe delay between retries based on `retry_delay`, until either a maximum\nnumber of retries have been reached or a maximum retry delay cap has been\nreached.\n\nGenerated from protobuf message `google.rpc.RetryInfo`\n\nNamespace\n---------\n\nGoogle \\\\ Rpc\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getRetryDelay\n\nClients should wait at least this long between retrying the same request.\n\n### hasRetryDelay\n\n### clearRetryDelay\n\n### setRetryDelay\n\nClients should wait at least this long between retrying the same request."]]
