I’ve forwarded this issue to the developers. Apparently it is caused by some weird identification duplication in one of our data sources.
I’m told it is not an easy fix, so it might take a while to sort it out.
2 Likes
