There are rare occasions where a vRealize Orchestrator workflow may become unresponsive or hung. In such a case, operators/admins are unable to cancel the workflow token. If such a thing happens and is not cleared even after a restart, then it may require delicate operation.

Step 1: Identify your running workflow’s token id

Every now and then I see a question come up that prompts me to do a little digging/experimenting. This brief article will address such a question. Last week, I saw the following request posted by a colleague:

Has anyone managed to configure the SQL plug-in with the embedded vRO PostgreSQL database?

For those unfamiliar, this is regarding the VMware vRealize Orchestrator (vRO) product that I used to work with regularly back when I ran the vCOTeam.info website (now archived here: https://vcoteam.github.io )