After a restart of Automation, VM deployments may fail with a Invalid credentials error message.
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".
Automation 8.1x
Any recent password changes made can cause an Orchestrator configuration element to no longer access Automation. The configuration element will continue to use the cached Access token for weeks or until a restart of Automation.
Post restart the cached Access token is cleared and must be reissued.
Run the workflow "Update vRA Host" to update the password.