Difference between Spawn All and Spawn New

I might be wrong but I'm under the impression that this is not very commonly used, and is tied more to legacy modes of operation.  However from what I know of it, basically it means you can loop over an MNI node multiple times where we assume the array PV the MNI is based on has had items added between executions.  "Spawn All" would re-execute the MNI for all items, whereas "Spawn new" would only execute it for items that have been added to the array post the prior execution.  This is explained somewhat in the mouse-over text, BTW.

That sounds right to me Mike.  And SPAWN NEW is something I've never had a use case for personally, in over a decade.

Essentially, say you have a reviewer who adds items A;B;C to an array.  The first iteration of Multiple Node Instances (MNI) will spawn 3 nodes for A;B;C.  Then a second reviewer appends 2 new items D;E to the array, resulting in A;B;C;D;E.  When the MNI node with SPAWN NEW is executed again, it executes 2 nodes for D;E, as A;B;C were executed prior.

That sounds right to me Mike.  And SPAWN NEW is something I've never had a use case for personally, in over a decade.

Essentially, say you have a reviewer who adds items A;B;C to an array.  The first iteration of Multiple Node Instances (MNI) will spawn 3 nodes for A;B;C.  Then a second reviewer appends 2 new items D;E to the array, resulting in A;B;C;D;E.  When the MNI node with SPAWN NEW is executed again, it executes 2 nodes for D;E, as A;B;C were executed prior.

Chris said:

SPAWN NEW is something I've never had a use case for personally

Same, and personally I'd be pretty leery in using it unless absolutely required to (and with some extensive testing).

Thank you Chris for sharing one use case, will try to replicate this in my POC