Our vCenter, vRA, vRO environment works fine, until last week where we had a couple of such messages too.
Just like you, on an action for an existing virtual machine.
We could not find any cause, so finally I rebooted the vRO machine and things went back to normal.
Perhaps there is a configurable timeout for this that can be extended to enable longer waiting?
nsajepi Where exactly (in vRA) did you find that re-configure option? I only see test/reset/update buttons.
Or did you use a workflow in vRO for that? (which I assume is not the place from where we can re-configure this connection)
Hi jimmyvandermast, I do this in vRA by going to Administration tab, vRO Configuration, Server Configuration, then entering my credentials in "Use an external Orchestrator server".