[NT-980] Updating the Optimizely events dispatch interval #1105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📲 What
Updates the dispatch interval for the
DefaultEventDispatcher
on Optimizely to 5 seconds to reduce likelihood of backend race condition.🤔 Why
The default dispatch interval on the
DefaultEventDispatcher
used by Optimizely to dispatch events and impressions was 60 seconds. This caused a race condition where sometimes the Kickstarter Ruby backend would attempt to send conversion event for an experiment whose "impression" hadn't been dispatched yet from the iOS SDK. By reducing the dispatch interval we hope to mitigate this race condition.🛠 How
dispatchTimeInterval
as part of theconfigureOptimizely
output.