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."],[[["The page details the `RetryPolicy` class within the `Google.Cloud.PubSub.V1` namespace, focusing on how it manages message delivery retries in Cloud Pub/Sub."],["Version 3.23.0 is the latest version available for the `RetryPolicy` class, with numerous previous versions also accessible, ranging down to version 2.3.0."],["`RetryPolicy` implements interfaces like `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and is constructed either with default settings or by copying another `RetryPolicy` instance."],["The class uses exponential backoff to determine retry delays, which are based on `MinimumBackoff` (defaulting to 10 seconds) and `MaximumBackoff` (defaulting to 600 seconds) properties, both of which can be set between 0 and 600 seconds."],["`RetryPolicy` retries are triggered when messages are NACKed or when their acknowledgement deadline is exceeded, though the actual delay may vary from the configuration."]]],[]]
