Execute VDB Action does not always set the correct VDB name in the VDB name property.

I haven't figured out why, but sometimes the Execute VDB action comes up with the right VDB name, and sometimes it comes up with the wrong name, and existing VDB, but not the one you're trying to execute.