Well, as I mentioned earlier, the ability to set a DataChangeTrigger that includes timestamp changes would mitigate this.
This “bug” is really interested to me, because in my view every one of the component systems (drivers, opc, ignition tags) is acting correctly, but only when viewed as a composite system the undesirable behavior emerges.
In a way, this is just a natural consequence of the fact that in a polling-based system you don’t get to see the value changes that occur in between polls, no matter how important they are to you.