When having calculationWaitTimeInSeconds set to a large value in combination with an AF-SDK app triggering recalculations, it can happen that recalculation writes a value at timestamp x before this analysis is triggered to run in real-time for timestamp x. This results in having 2 events in the archive, for the same timestamp. When having EFs making a summary eventweighed, this results in a wrong value being captured as some events will be counted twice.
