Not sure why this would be causing a loop issue? its explicitly told not to trigger on all of the states its updating
Looking at the payload in the error, it seems as though GrossPoints was the attribute received, which is not in the ignore list. Is that being reported from somewhere else in this same workflow?
By workflow if you just mean connected nodes then no, this is the only state update in this connected part, which from the above image has the the payload next to it that was submitted.
I misunderstood the re-entrant check. What’s being blocked is the Device: State Node, not the trigger. The ignore list has nothing to do with this specific error check.
This error was received because the Device: State Node is being executed under a Device: State Trigger that itself was triggered because of a Device: State Node in this same workflow. That is detected as an infinite loop and is blocked.
So I would have to separate all of the device state triggers into their own workflows to prevent these errors?
Not that its necessary an issue since I’m not missing out on anything
For this issue, yes, you can split the logic into separate workflows. Just be careful you have all the attribute filters properly configured. It can be easy for workflows to infinitely trigger each other consuming tons of payloads. The reentrant check is there to prevent that from within a single workflow.
1 Like