You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+58Lines changed: 58 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,6 +154,64 @@ public class Sample {
154
154
```
155
155
`isIdempotencyReplayed()` method can be accessed to differentiate between original and replayed requests.
156
156
157
+
158
+
### Retry HandlingAdd commentMore actions
159
+
160
+
Chargebee's SDK includes built-in retry logic to handle temporary network issues and server-side errors. This feature is **disabled by default** but can be **enabled when needed**.
161
+
162
+
#### Key features include:
163
+
164
+
-**Automatic retries for specific HTTP status codes**: Retries are automatically triggered for status codes `500`, `502`, `503`, and `504`.
165
+
-**Exponential backoff**: Retry delays increase exponentially to prevent overwhelming the server.
166
+
-**Rate limit management**: If a `429 Too Many Requests` response is received with a `Retry-After` header, the SDK waits for the specified duration before retrying.
167
+
> *Note: Exponential backoff and max retries do not apply in this case.*
168
+
-**Customizable retry behavior**: Retry logic can be configured using the `retryConfig` parameter in the environment configuration.
169
+
170
+
#### Example: Customizing Retry Logic
171
+
172
+
You can enable and configure the retry logic by passing a `retryConfig` object when initializing the Chargebee environment:
0 commit comments