The following is true:
This is a known issue and it has been fixed on the newer releases of SpanVA (1.15.3.140+), upgrade the Spanva instance to the latest, restart the instance on the new release and test again.
if the issue persists, Open a support case.