RetryPolicy will be triggered on NACKs or acknowledgement deadline exceeded
events for a given message.
Retry Policy is implemented on a best effort basis. At times, the delay
between consecutive deliveries may not match the configuration. That is,
delay can be more or less than configured backoff.
[[["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-03-31 UTC."],[[["This page details the `RetryPolicy` class within the `Google.Cloud.PubSub.V1` namespace, which is used for managing message delivery retries in Cloud Pub/Sub."],["The latest version documented is 3.23.0, and the page provides links to documentation for versions ranging from 2.3.0 to 3.23.0, including several versions in between."],["`RetryPolicy` utilizes an exponential backoff strategy for retries, with configurable minimum and maximum delays, to define how often messages are retried."],["The class implements several interfaces including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and has a constructor that can initialize a `RetryPolicy` instance."],["Key properties of `RetryPolicy` include `MaximumBackoff` and `MinimumBackoff`, which allow users to define the duration bounds for message redelivery delays."]]],[]]
