There currently is no resolution for this issue. A change request has been submitted with the product team for resolution in a future release. Please continue to monitor release notes of future versions to see if this defect has been resolved.
Workaround 1.) Simply restart the vasproxyd service (i.e. systemctl restart vasproxyd)
Workaround 2.) Reboot the client