Skip to content

Conversation

@jaeopt
Copy link
Contributor

@jaeopt jaeopt commented Jan 26, 2026

Summary

This PR increases the maximum retry time interval to 3 seconds across retry mechanisms in the Python SDK. This change optimizes retry behavior by ensuring consistent maximum wait times during failed requests.

Changes

  • Updated max_retry_interval from 1.0 to 3.0 seconds in optimizely/odp/odp_event_manager.py
  • Updated DEFAULT_MAX_BACKOFF constant from 10 to 3 seconds in optimizely/cmab/cmab_client.py
  • Updated comments to reflect the new 3-second cap for exponential backoff

Jira Ticket

FSSDK-12248

Testing

  • Existing unit tests should pass with these configuration changes
  • Retry behavior will cap at 3 seconds instead of previous values during exponential backoff
  • ODP event retries now have consistent maximum interval with CMAB requests

Notes

  • This is a configuration change that standardizes the maximum retry wait time across different SDK components
  • No breaking changes or API modifications
  • Reduces maximum wait time for CMAB retries from 10s to 3s while increasing ODP retry max from 1s to 3s

@jaeopt jaeopt closed this Jan 26, 2026
@jaeopt jaeopt deleted the ai/jaeopt/FSSDK-12248-retry-interval branch January 26, 2026 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants