Octopus and Galapagos (and most other solvers i guess) are setting a new value to the parameters, then set the ‘expireSolution’ flag on those components which makes all downstream components (all the dependencies of the parameters) update themselves. this, afaik, is happening in one go to the normal ‘user’ (say plugin-coder), and cannot be interrupted. after this, the newly computed values at the objective-components are read and collected by octopus / galapagos.
however if you work with timers, dataDams, any kind of loops, this behaviour of grasshopper (some call it ‘state-less’) might be disturbed. make sure your definition does not use any of those ‘hacks’ to the default behaviour.
best
R