There are many points in my app in which I have to use the “while loop workaround” of a bunch of on-step enter steps but I now have multiple instances in which I’m hitting the 100 trigger limit, and I’m not in an infinite loop, it’s just the nature of the operation, and in most cases is exacerbated by the lack of nested-if statements. So I’m obviously pushing up against / exceeding the limits of what “native” Tulip can do and I am wondering what would be the best direction to go for expanding functionality, particularly more advanced logic. I’m performing a lot of Tulip Table querying and combining results from multiple tables into one array or a new “temporary” table for displaying information in a different way. I need to to be able to read from and write to Tulip Tables and the number of traditional Tulip triggers happening is in the hundreds although performing the same actions in Python or any traditional programming language would probably be ~50 lines or less of code.
Would writing the logic within a connector be the best way to go forward? I thought there was a limitation with connectors only being able to return variables that I’d then have to write to a Tulip table. Would using node-red as my “language” and a connector work? Some other option?
Thanks for the input!