After a restart of Automation/Orchestrator, workflows and actions may fail with a Invalid credentials error message. This can have a knock-on effect on VM deployments.
Example of failure:
Action 'Action name' in module 'Module name' failed : Failed to get VMware Aria Automation refresh token. Invalid VMware Aria Automation credentials provided. (Dynamic Script Module name : "Action name"); [1]
["A] undefined; [2][t][Action name] undefined.
vco-server-app.log will contain an error "Invalid VMware Aria Automation credentials provided".
VMware Aria Automation 8.18.x
Any recent password changes made can cause an Orchestrator configuration element to no longer access Automation.
The configuration for the Automation host will continue to use the cached Access token for weeks.
Run the workflow "Update vRA Host" to update the password for Automation used in Orchestrator.