@mlauber71 yes, I agree. This falls into the bucket of hard to trace problems we keep a record of. Though, it still causes concerns as no one can actually tell if there is a problem or not.
It is almost as if the node is in a quantum state of superposition
I also just experience another odd behavior where that very same node got triggered to execute but was kind of hanging not starting to crunch the data. No error … just “superposition” oof awkwardness.
PS: I start to believe there is a more fundamental issue as I encountered something similar before but with the Component Output. Just right now I got this “experience”.
Kind of similar to what I reported in:
@marc-bux FYI - as follows the thread dump in case this is of any help
241024 Execution finished but nodes still running threaddump-1729790274758.tdump.txt (102.1 KB)