I am 100% guessing here, so please don’t take anything in this post too seriously.
I have an internal, unvalidated assumption that a repeating group will update automatically if the data source is something like, “Current User’s Stuff.” I also have an internal, unvalidated assumption that a repeating group will not update if the data source starts with, “Do a search for…”
Why do I think this? In my mind, the “do a search for” seems to tell me that it’s grabbing a snapshot of all the data that matches that query at the time the query was made, while the “Current User’s Stuff” is just returning all the entries on that list.
Like I said, I haven’t tested it and could be totally wrong, but in my tiny little bird-like brain, this is what was invented as an answer.
And i don’t understand how bubble users can go on with their lives and not being bothered by this problem. any app probably uses multiple repeating groups with constraints.
Its the first app i’m building in bubble, and if this problem is here to stay, i dont see how i can use that app.
As a sanity check add a custom state Boolean and toggle this when you make a change or whatever. Set to conditioning in your repeating group based upon this for a different source but with the same conditions, this forces the situation may help validate what the issue might be.
I actually use this for API calls in repeating groups which will only actually refresh on a page refresh which is obviously not conducive to the user experience. I simply create exactly the same API call with all the same conditions just give it a new name and then when the custom state changes set the repeating group to the 2nd API call which is actually exactly the same as a 1st. Seems to work okay