Reloading historical data does NOT solve the issue. Last time this problem occured, some of Ninja's Datastreams were offset and caused the conflict. Need a solution now.
(Note: I did also open Platform Support Request 1557045 for this issue a moment ago)
Comment