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 provides reference documentation for the `RetryPolicy` class within the Google Cloud Pub/Sub v1 API, specifically detailing its implementation for managing message delivery retries."],["The `RetryPolicy` class implements multiple interfaces, including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, indicating its role in message handling and data structures."],["The API supports numerous versions, ranging from the latest version 3.23.0 down to version 2.3.0, allowing users to select the specific version they are using."],["`RetryPolicy` allows for configuration of both `MinimumBackoff` and `MaximumBackoff`, which define the minimum and maximum time between retry attempts, with default values of 10 and 600 seconds respectively."],["The retry mechanism is triggered by NACKs or when the acknowledgement deadline is exceeded for a given message, and the system uses exponential backoff to manage retry delays."]]],[]]
