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
log.Warn("Timed out waiting for Eppo SDK to initialize")
48
+
}
43
49
}
44
50
```
45
51
46
52
After initialization, the SDK begins polling Eppo's API at regular intervals to retrieve the most recent experiment configurations such as variation values and traffic allocation. The SDK stores these configurations in memory so that assignments thereafter are effectively instant. For more information, see the [architecture overview](/sdks/architecture/overview) page.
47
53
54
+
### Waiting for initialization
55
+
56
+
Depending on your server application's lifecycle, you may need to wait for the SDK to initialize before making assignments
57
+
58
+
Starting with the `6.1.0` tag, the `Initialized` channel is provided to facilitate this and can optionally be used with a timeout to allow you application to continue.
59
+
60
+
Before this tag, the SDK was initialized asynchronously and assignments could be made immediately but will not be guaranteed to have the most recent experiment configurations, returning the `DEFAULT-VALUE` if the SDK was not initialized in time. If this is not desired in your application, a suggested approach on older versions is to introduce a brief delay after startup to allow the SDK to initialize before making assignments.
### Define an assignment logger (experiment assignment only)
49
79
50
80
If you are using the Eppo SDK for experiment assignment (i.e randomization), pass in a callback logging function to the `InitClient` function on SDK initialization. The SDK invokes the callback to capture assignment data whenever a variation is assigned.
0 commit comments