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 latest version available for the Google.Cloud.PubSub.V1 API is 3.23.0, with multiple versions back to 2.3.0 documented, allowing users to browse documentation across these different versions."],["The `RetryPolicy` class within the Cloud Pub/Sub v1 API is used to define how the system handles retries when delivering messages, specifically when NACKs or acknowledgement deadline exceeded events occur."],["The retry delay implemented by the `RetryPolicy` class follows an exponential backoff strategy, although there might be slight deviations from the configured delay times in practice."],["`RetryPolicy` has two properties that can be set, `MaximumBackoff` which sets the max delay and `MinimumBackoff` which sets the minimum delay between message deliveries."],["`RetryPolicy` implements multiple interfaces including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and has two constructors: a parameterless one and another that takes another `RetryPolicy` as a parameter."]]],[]]
