No, we try to freeze a “state of the universe” at the beginning of a workflow execution, and only reflect changes when the workflow explicitly modifies something. Things like a cell in a repeating group showing a different thing we don’t count as an explicit change. That said, our rules for how exactly that works aren’t great: they’re pretty complicated (I sometimes have to read the actual Bubble source code to predict how a particular situation will play out), and they don’t handle interactions between workflows well (if two different users modify the same data at the same time, the end result might ignore the changes made by one of the users), so this is fairly high on our todo list to overhaul: I’d like to be in a place where we have a clear, easily understandable set of guarantees we can make about how data will behave.
Forum
Academy
Marketplace
Showcase
Pricing
Features