Never mind, appears to be due to an issue with one of the dependencies of the RemoteExec resource. Problem is gone.