Hi Krona,
If that's the case, then, there should be no duplicates because we won't generate a set of events with an extra record.
How can we schedule a call? We've made all sorts of changes and test cases to support you guys, but we're not anywhere closer to solving our original problem. This has been going on for 2 months...
Our biggest issues as I understand them are, assignmentStore calling onRemove handler in the pro project model approach, the deduplicating the events -- to prevent duplicate drop artifacts (we already use skipTokens, but there's a guarantee that a race condition will apply under the hood), 'jerkiness' from race condition updates (event moves back to the original location during an update, then after the update is performed, moves back to the final location).
