carl1's Accepted Solutions

So you are runing 3 vRO instances (even if you are a single vRA node).  The workflow that is changing the value is likely running on a different node than that which is checking it's value.  Config E... See more...
So you are runing 3 vRO instances (even if you are a single vRA node).  The workflow that is changing the value is likely running on a different node than that which is checking it's value.  Config Elements are cached in RAM. So if vRO 1  checks the value vRO 2 changes it (but this is in the vRO DB only) vRO 1 checks the value again but the cache has not changed So what you need to do is do a "config_element.reload()" to load the new value.  If there is any chance that more than one vRO workflow could change it at the same time, you will need to set a mutex lock to ensure only one running workflow changes it at a time. For example, here is a code sample that gets sequence numbers.  Sorry it is in XML form but you can get the idea.  My lab is not up tonight. Carl L.
I created a WF to do just that.  Take a look on flowgrab for nestedesxiinstaller and the WF "Run SSH command With Timeout".  It's not the prettiest thing but it works . Carl L.
Yes.  It is just another instance of vCO that you can use.  Carl L.