This bug is also present in WFA 18.104.22.168.0 build 3858982. Since we dont use parent vserver, the workaround is fine for us. Adding the "-Vserver $VserverName" in the PowerShell code was necessary for us to talk to ONTAP 8.2 and 8.3 clusters.
FYI to others...we use WFA4.0, OCUM 7.1, CDOT 8.2 and 8.3. Had to modify the 'Clone Volume' command and add the [-Vserver $VserverName] switch to the powershell code (highlighted in the screenshot below). Since you can't modify a signed command you have to hit "save as" and rename it. You'll then need to replace the command in your workflow. I'm hoping to test on 9.1 soon.
Cmdlet used in the Clone Volume command is acting in the controller contest, and when we pass junction path as a parameter, it should work in the Vserver contest, presently which command is not able to handle .
The fact, the ZAPI/Cmdlet used in the Clone Volume command can act on both the contexts, vserver as well as cluster(controller).
This command has been used in the SVM_DR pack as well where that should work on cluster context when user will pass the parent vserver name ($ParentVserver).
We have already fixed this issue and it’s in review, it will be part of 1.2.2 pack.