Custom Resource Actions Disappear from Deployment Menus Following VCF Automation 9.1 Upgrade
Article ID: 453195
Updated On:
Products
Issue/Introduction
After upgrading VCF Automation from version 9.0 to 9.1, custom Day 2 resource actions may disappear from the execution menus at both the Machine and Deployment levels.
Observed Symptoms:
Custom Resource Actions no longer populate in the Day 2 actions drop-down menu for end-users.
Entitlement and Day 2 policies remain fully intact, with the appropriate scope and project assigned.
The Custom Resource Actions still exist and are visible within the design interface, but they fail to render on deployed resources.
No explicit error message is displayed in the UI (the actions are simply suppressed).
Environment
Product: VCF Automation / VCF Orchestrator (vRO)
Version: 9.0 upgraded to 9.1
Cause
The upgrade from VCF Automation 9.0 to 9.1 severs the backend database mapping between VCF Automation Custom Resource Actions and their underlying VCF Orchestrator (vRO) workflows.
During the upgrade process, schema or communication changes between Orchestrator and Automation break the existing workflow linkages. Because VCF Automation can no longer validate the execution path to the targeted vRO workflow, it safely suppresses the actions from the resource drop-down menus to prevent runtime execution errors—even though the entitlement policies remain active.
Resolution
To restore the missing Day 2 actions, the mapping between each Custom Resource Action and its corresponding vRO workflow must be manually refreshed in the administrative console.
Step-by-Step Execution Plan
Access Custom Resource Actions: Log into VCF Automation and navigate to the Design > Custom Resource Actions menu.
Open Affected Action: Select and open the first affected custom resource action.
Re-bind Workflow: Browse and re-select the appropriate VCF Orchestrator (vRO) workflow that powers the action.
Save Changes: Click Update (or Save) to commit the change.
Repeat: Repeat steps 2–4 for all remaining affected custom resource actions.
Verify: Navigate to an active Machine or Deployment and open the actions menu to confirm that the custom Day 2 actions are now visible and executable.
Additional Information
Re-selecting the vRO workflow and saving the configuration forces VCF Automation to rebuild and validate the linkage to VCF Orchestrator in the backend database. Once this relationship is re-established, the platform recognizes the action as valid and executable, immediately restoring it to end-user menus based on the existing Day 2 policies.
Feedback
