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 `RetryPolicy` class in the Google Cloud Pub/Sub v1 API allows for the configuration of message delivery retries, employing an exponential backoff strategy."],["This `RetryPolicy` is triggered by NACKs or exceeded acknowledgement deadlines, and it works on a best-effort basis, meaning the delay between message redeliveries may vary from the configured values."],["The documentation lists a range of versions for `RetryPolicy`, with the latest version being 3.23.0, and is implemented using several interfaces such as `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`."],["`RetryPolicy` has properties for `MaximumBackoff` and `MinimumBackoff`, determining the maximum and minimum delay, respectively, between message redeliveries, with default values of 600 seconds and 10 seconds."]]],[]]
