Hi,
I have created a dynamic type object that has about 20 properties. When I create the object in the external system, it takes about 5-8 minutes for the IP address property to get populated. Before its populated, it has a value of [].
I have a workflow that uses this property after it creates the object, so I want my workflow to pause and wait until this property is available to use.
So I have something like this in scriptable task
while (AHV-VM.getProperty("ipAddresses") == "[]") {
System.log("Waiting for IP address to be populated...")
System.log(AHV-VM.getProperty("ipAddresses"))
System.sleep(15000)
}
My problem is that even after the IP address gets populated, this loop never stops. It prints the old value even though the object is updated in vRo. Also, if I click on the workflow run variables, the IP shows in there as well. So it seems like this scriptable task caches the object properties and isn't reading any updates in the while loop.
If I cancel the workflow and run it again, it works fine (while loop doesn't run and workflow proceeds). So is there a better way to approach this? Any reason why when the loop evaluates the condition, the property isn't being updated?