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, focusing on how message delivery retries are handled in the Cloud Pub/Sub service."],["The latest version of `RetryPolicy` is 3.23.0, and the page provides links to the documentation for versions spanning from 3.23.0 back to 2.3.0."],["`RetryPolicy` uses exponential backoff, with configurable minimum and maximum delay values, for retrying message delivery on NACKs or acknowledgement deadline exceeded events."],["The class implements multiple interfaces, including `IMessage`, `IEquatable\u003cRetryPolicy\u003e`, `IDeepCloneable\u003cRetryPolicy\u003e`, and `IBufferMessage`."],["The `RetryPolicy` class offers two constructors, a default constructor, and one that takes another `RetryPolicy` object, along with two settable properties: `MaximumBackoff` and `MinimumBackoff`, that define the retry delay behavior."]]],[]]
