The required action is to perform an inventory sync . In VCF Operations Fleet Management, vertical scale-up depends on current inventory data from the managed component. The scale workflow first validates that the Fleet Management appliance has an accurate view of the VCF Operations cluster, including node inventory and placement information. The documented vertical scale-up workflow states that after selecting Fleet Management > Lifecycle > Components , choosing the component, and selecting Vertical Scale Up , the administrator must acknowledge the downtime warning and click Trigger Inventory Sync to synchronize the VCF Operations Fleet Management appliance with the latest data from the cluster. After the inventory sync completes successfully, the administrator can click Proceed and continue selecting nodes and target scale-up sizing . Mandatory snapshots are not the corrective action for stale inventory. Taking the cluster offline is not the manual remediation for the "Needs Attention" inventory condition, although nodes are restarted during the scale operation. Scaling Cloud Proxies is unrelated to vertically increasing VCF Operations management- node resources. Reference topic: Objective 4.14 - Complete Fleet Management activities in VCF Operations / scaling VCF Fleet Management Lifecycle / vertical scale up for VCF Operations .

The scheduled oversized action remains valid for acme001, so the VM is reduced by 2 vCPU . Excluding the VM from the undersized list affects subsequent undersized resize actions, not the oversized action that was already scheduled. VCF Operations Rightsize separates oversized and undersized workflows. For oversized VMs, the administrator selects the Oversized VM tab, optionally excludes VMs, selects the target VMs, and schedules or runs the resize action to reduce vCPU or memory . For undersized VMs, the administrator separately selects the Undersized VMs tab, optionally excludes VMs, and then schedules or runs the scale-up action . The Rightsize table explicitly provides separate actions for oversized and undersized VMs, with Schedule Action , Resize VM(s) , and Exclude VM(s) available within each category . Because acme001 was selected for the oversized scheduled action before any undersized exclusion was applied, its vCPU reduction is still scheduled. Because the administrator then excluded acme001 from the undersized list before scheduling the undersized scale-up for the remaining VMs, acme001 is not included in that memory increase.
Reference topic: Objective 4.2 - Rightsizing / Oversized and Undersized VM Actions / Exclude VM(s) / Scheduled Actions .