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.