Determine cause for importance of order in state update in Process.on_entered
#5817
Labels
priority/quality-of-life
would simplify development
topic/processes
type/question
may redirect to mailinglist
In #5813 a very subtle bug was fixed that was introduced by swapping the order in which the outputs of the node and the process state attribute were updated. Reverting the order would cause the nightly workflow to fail since one of the many workchains that would be run would fail because one of the subprocesses (although finished successfully) would not have the outputs attached. For now the order is reversed to the original order which fixes the problem, but it is not understood why the order matters at all.
The text was updated successfully, but these errors were encountered: