RP4VM 5.2.2.0 - issue with powering on target vm's when they're inside vapp container

Has anyone tested protecting vm's that are inside a vmware vapp container with RP4VM 5.2.2.0? I'm seeing this issue in multiple 5.2.2.0 environments, but not in 5.2.0.1. I can protect VM's, but any time RP4VM is trying to power on the target vm it fails to do so with the error below. If I take those same VMs out of the vapp container it works fine. ""The copy [PT-test-viprsrm-cg, copy1] is regulated because RecoverPoint failed to power on a VM, possibly because the production VM hardware reservations cannot be applied on the remote VM. Disable image access, reduce the production VM hardware reservations, and perform image access again."" -Peter