Hello Team,I'm using a MNI startprocess with the Run one instance for each item in pv!array (spawn all) along Run all instances at the same time(move when All instances are done), in process parameters I'm sending pv!array[tp!instanceindex] to another process.In one scenario I have only one element in pv!array, but it triggered 2 instances for the same data. Could anyone explain me why this happening?Stefan Helzle
Mike Schmitt
Discussion posts and replies are publicly visible
Have you posted any image ?
May be the array contains null value. Check the size of array.
I checked in process history, I have only one value inside that array and I'm also having xor to check the null values.
More details please. I would really like to see the process variables in that affected instance.
How do you do this null check?
As you can see I have only one message here, but it triggered 2 instances for the same data.
That null check only checks whether the list is empty, but it does not check or remove any null value items in the list.
Your configuration seems to be OK. How do you know the number of instances?
the null won't be an issue I guess, because the variable will receive either 0 or more items only.
Stefan Helzle said:Your configuration seems to be OK. How do you know the number of instances?
In monitoring I got an error stating that "The relationship between the task and the employee is already in the Data table" from a write to DSE node. Meaning the first instance wrote that relationship already, and the 2nd instance trying to do the same. using process display name I found this, 2 instances for the same data.
OK. And when monitoring the parent process instance, what do you see when right-clicking that sub process node?
It will always show 1 instances only, as I kept "Delete previously completed/cancelled instances"
OK.
So, to recap: You have a list with exactly a single item and expect that MNI node to run exactly a single time. But you see two process instances. This means, that either that list contains more than one item, or your observation, two process instances, is wrong. You will have to find a way to proof these expectations and observations.
I have never seen any misbehaviour when configured correctly.