This issue was terrible in my app today, causing lots of issues for our users. Maybe worst I’ve ever seen it.
Something else I’ve thought of though that could alleviate this, is a feature that’s been requested before, which is a way to force refresh RGs.
Even if this particular bug is fixed, there are still lots of nasty caching issues, particularly in mobile Safari, that block the auto refresh. Having a way to force the refresh manually would not only be a short term fix to this bug, but also any and all other auto-refresh blocking bugs.
Here are some other threads on this feature/other rg refresh bugs:
The auto refresh ability of Bubble RGs is cool, but it’s never been truly reliable 100% of the time, and there’s no reason for us to believe it ever will be in the future. So does it not make sense to provide the ability to manually trigger refreshes as a backup?
Sharing screenshot as ideaboard ideas don’t have url to share.
By the way, for me the issue is not limited to having new data not getting updated in RG. What also happens is that wrong data is shown in the table because of broken connection or whatever. So for example if it is a repeating group that shows a list of tasks, then in the row of tasks one column will belong to one task, another to another task etc. It quadruples the confusion and issues.
PS: Also, I think there are some kinds of threads (don’t know which kind) which don’t expire. Maybe we should figure that out and post one of that kind.
Yeah, so the second band-aid fix we tried worked, and the problem hasn’t occurred again since. We don’t think this fix will last forever, and are still working on the long-term fix, but so far so good.
For users such as @gaimed who are still seeing a problem, it may be a different issue than the one we’ve been looking into, so I encourage opening a bug report with details about your specific app if you haven’t already to make sure it gets on the team’s radar.
I’m passing on the force-refresh feature idea to the team. It’s an interesting idea, but I’m not sure if it would solve caching issues, since those tend to be at a layer below our code; we’re already trying to force a refresh whenever we detect the data in the repeating group is stale. More likely, the best route forward there is for us to find a workaround to the caching problems that makes our existing real-time updates just work without users having to write a workflow.
hi @josh if you consider implement the idea of workflow force refresh the repeating group, maybe is more faster than other paliative solutions… at least it would give time to implement a definitive solution.