Real-time data doesn’t seem to be working in Live version. Anyone?
I’ve got the same version in LIVE and a DEV branch.
DEV: trigger workflow which creates a item in the DB => it immediately shows up in the adjacent repeating group.
LIVE: same steps => nothing shows up in the repeating group. Data shows after refresh.
Creating things in backend and seeing them real-time in frontend has issues. It’s impossible to replicate unfortunately. I see it some times and not others. I haven’t found a solution. It was not a browser extension issue either.
Unfortunately we’re having the same issue in both DEV and LIVE. What’s even more frustrating is that we experience this with the Schedule API workflow on a list, so there’s no way to know when the last item got created. For your case, @rico.trevisan, a clear group + display data in group might work?
PS: I’ve flagged this to Bubble a couple of days back, I’ll keep y’all posted here
I don’t think this will, as the search is still cached behind the scenes as your browser hasn’t been told by Bubble’s notifier that the search result has changed.
I’ll make a bug report too and link all of the threads. I know it’s hard for them to debug when it’s not consistently reproducible but it’s definitely happening at some scale.
This is completely untested but I’d be curious if you could force a search with a created date constraint (similar to force refreshing with header times)
Something like on create button click
Clear list
Set list (same search :merged with do search for same search but with same search but with created date < current date time +minutes -1)
Only reason id use merge list is to have both the original search that is cached & the second one with a date field that we may be able to force refresh cache.
Would need a very slight delay to account for backend processing time just in case
Thanks George, quickly thinking on top of my head here - could this work if the new search had an extra constraint created date > current date: +yrs: -50?. I’m currently not at my pc to test this unfortunately.
Yeah possibly. The current date time might not update in the search though (even though, due to the laws of physics, time of course has passed). Making a custom event that returns the current time is what I do in the backend to ensure that I can record the start and end time of operations (as referencing Current date time directly only references one time for the whole workflow). I’d assume this works in the frontend too.
That said, not really something we should have to do and it definitely needs to be fixed. It’s been happening for at least 3 months.