I got this:
Our engineering team informed me that they deployed a fix last Friday that may have resolved this behavior. Would you be able to confirm if you’ve experienced any issues with repeating groups this week?
Which seems to indicate they did make an actual fix rather than assuming it’s fixed. @J805 have you seen the issue since then?
Hmm. I will check.
seems like the first you create it works, the second doesn’t then create a 3rd and the 2nd and 3rd will then show, then that’s pretty consistent thereafter, where create, doesn’t show, create again and last 2 show at same time.
Yeah, that is what happens in my app too.
Sorry I just want to chime in on this. This is just different people doing the same thing… in the same app.
If nothing happens then nothing happens.
If the bug can be repeated then all it shows is that there’s an issue with the way the app is built.
If it happens to some and not to others then it just looks like it’s a client side issue (browser, extensions etc).
It has to be able to be reproduced, not just repeating the bug with the exact same parameters. The issue is that this bug affects some apps, not all apps. Furthermore, from reading everyone’s anecdotes, in some apps it doesn’t happen all the time.
From a troubleshooting perspective there’s a lot of variables to pin down and not everyone provides detailed bug reports. A better method is if a group of people created test apps/pages to try to reproduce the issue and share the data (what/how it was done etc) in one thread. Just like how @adamhholmes does in his threads.
In any case, I hope Bubble fixed the bug.
Exactly my experience. My second run thru, I waited at least 5 seconds after the 2nd and it hadnt shown up yet. Aftet the 3rd, 2nd and 3rd showed up together about 1 second later
Yes, I’ve seen some take a while (sometimes 5-10 seconds), but didn’t think that was enough to report as a bug, even though I know in the past it’s always been virtually instant.
At least we have a test sandbox - next time you see it in your own app, try it on this test app too and see if it happens on both
Here is an example of where it is still giving issues. Although, it seems to have improved. It takes longer to break now. It used to be pretty quick when it would break. Now I have to use the app for a while before it breaks. So at least we are moving the right direction. Here is a screen recording. When I add a column called ‘Status’ then it finally breaks and doesn’t show up anything until I refresh the page.
Ran into this again just now and I am able to reliably reproduce the bug on a client’s app (at least for the last 10 minutes)… We create a user in the backend, and it doesn’t appear in the RG until page refresh.
At the same time, it works fine on the test app. That means that at least to some extent, the issue is app specific rather than across the entire Bubble ecosystem. Just because one of your apps has the bug appearing, doesn’t necessarily mean every app you work on will be experiencing the issue right now.
Reported the bug again and we’ll see what happens.
I hope that helps the team diagnose the issue. I wonder if it’s a privacy rule bug or something. 
Hi @J805, hi @georgecollier
Somehow related to the subject, if you’re using “database trigger event”, there’s a 100% chance that it impacts the information displayed in real-time in a repeating group.
More precisely, when you’re able to delay that “database trigger event” for a few seconds, you’ll see your real-time data appear in your repeating group (if fetched by an API call and stored in your database) and then disappear once the “database trigger event” really starts.
Oh my, I spent days and days on that. I can even tell you that the database trigger event was developed by a Bubble intern some time ago as I compiled all the existing information at the time. The only solution I found: not using any database trigger event at all.
Regards,
I actually never use database triggers. The only time I might use that is if I’m trying to sync a database from Bubble to something like TypeSense. 
Thanks for sharing.
GUYS! Does your affected data type involve privacy rules that have ‘X’s List of Y contains This Thing’
(i.e the privacy rule is granted based on its presence in a list)
I’ve just solved this in my app.
I did not have data updating when creating an account for another user.
This privacy rule will result in the page needing to be refreshed, even though it’s 100% evaluated as true (as evidenced by the fact it works when the page is refreshed.
This privacy rule will result in the table being updated in real time when a new thing is created:
This bug, or at least part of it, is caused by a privacy rule that involves a List of X.
I think we are onto something. I do think we are correct that it is a privacy rule ‘issue’. I rarely use a list and this time I need to. So it’s most likely causing the issue. Maybe we can send Bubble our findings so they can fix it. Go team! 
I sent them the video as well, along with a longer explanation… this is 100% the issue for my app (and I can tell because I reliably and predictably reproduced it in my video). Should Bubble have worked this out months ago? Yeah, probably, but at least we’ve got it now… I’ll report any updates on the bug fix here.
That’s good to hear. Makes sense. My gut was telling me it was a privacy issue some how. Not sure how they will fix it, but at least you have reproducible steps. 
Update…
For me, I struggle to see how it can be classified as expected behaviour if a privacy rule updates in real time with one constraint, but not with another constraint… and works on front end, but not on backend. Pretty obvious that it’s a bug. Unfortunate, but that’s the response and it’s here to try.
For anyone that stumbles across this thread in future, the bug is at least sometimes caused by privacy rules that references Current User’s X List of Y contains This Y. There may be other constraint structures that cause it.
Changing it so it’s Current User’s X is This Y’s X means it works fine.
I still have this problem - and it is dragging my energy level down below 0.
@christina.sandberg Have you been able to test if yours is also a privacy rule issue?
