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
The current implementation of using experiment start timestamp as its identifier can cause problems as the uniqueness of the ids cannot be guaranteed. For instance, when two experiments start "simultaneously", both of them are assigned the same timestamp as an identifier. Consequently, all telemetry associated with this identifier gets mixed up, which can lead to confusion and incorrect data analysis.
The text was updated successfully, but these errors were encountered:
The current implementation of using experiment start timestamp as its identifier can cause problems as the uniqueness of the ids cannot be guaranteed. For instance, when two experiments start "simultaneously", both of them are assigned the same timestamp as an identifier. Consequently, all telemetry associated with this identifier gets mixed up, which can lead to confusion and incorrect data analysis.
The text was updated successfully, but these errors were encountered: