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 to define how Cloud Pub/Sub retries message delivery."],["The latest version documented is 3.23.0, but the page contains version history ranging from 2.3.0 to 3.23.0 with the page being specific to version 2.6.0."],["`RetryPolicy` implements multiple interfaces, including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and inherits from `Object`."],["The `RetryPolicy` class has properties for `MinimumBackoff` and `MaximumBackoff`, both of which are of type `Duration` and control the delay between retries, with default values of 10 seconds and 600 seconds respectively."],["The retry mechanism for message delivery is based on exponential backoff, and it is triggered by NACKs or acknowledgement deadline exceeded events."]]],[]]
