Wait for Adapter is skipped for VPN Entry Opening via Opening RDP Session the same as the last one closed to trigger the VPN Group Close VPN

Howdy Folks,

Hopefully the title will make perfect sense once I have set the stage a bit (or maybe it makes perfect sense standalone, one can only hope, but one will also explain anyway)!

I have setup VPNGroups on a number of RDP Session entries as-per their environmental separation paradigm, and by far the RDP Session entry I use more than any other RDP Sessions combined is my Virtual Developer Machine in the DEV environment.
To that end, that is pretty well always the one that is first to be opened and last to be closed.

The problem I face in this situation, is that if I've got a 'Wait for Adapter' setting set on the VPN entry which is linked to the RDP Session (ie: the RDP session VPN section doesn't have a Wait for Adapter set, but the linked VPN session VPN section does), if I open the same RDP session as the one that was most recently closed and which caused the VPNGroup to close the VPN session...
It does the 'ping for host' check as expected, then failing to find the host, starts the VPN session as expected, but it fails to apply the 'Wait for Adapter' check configured in the VPN session and skips straight to the 'Then Delay' portion instead.

It will successfully 'Wait for Adapter' if I first open any other RDP session in that VPNGroup, if I open any other RDP session under a completely separate VPNGroup, or if I manually explicitly run an additional 'close' on the folder containing the VPN sessions.
(The sessions are FortiClient type VPN Sessions by the way)

I have since added the 'Wait for Adapter' check onto the RDP sessions themselves as well, and those are triggered as expected, so it's not the worst problem in the world, but it's a strange little bug.

Happy hunting!