This sounds like you are having similar issue to the one I posted in the thread just below/before yours. For some reason, WL Bulletin closes and WL stops reading data. VVP then doesn’t appear to handle this well and eventually gets “stuck” itself, no longer reading data from the VP console and instead sending the same stale data to WD.
Previously (3.5 years) I was using virtual serial ports instead of TCP/IP and when the WL Bulletin closed VVP was unaffected and in turn WD was unaffected. WL 5.9.3 seems much better but I have always had flakiness with WL, though a simple restart of WL got it back where it should be with no other impact. Now that I have switched to network instead of serial, WL has become more unstable and VVP is now affected adversely 