Looking for some advice. I have some spot solutions but wondering if there is a broader best practice. In general, I have backend workflows that change things in the db. I need the changes to get reflected in the front end roughly real time so users see the results when they happen. My app is mostly on a single page so I can’t depend on page navigation refreshes. Is there any best practice design/workflow technique that can help with this? Thanks!
If you are using Bubble DB, it should be updated in realtime (if you don’t set data into a state)
1 Like
Currently my backend workflow adds something to the DB that should show up in a repeating group and it updates a date field that’s on a contact record. I’ve been able to replicate it twice that it doesn’t update all the time on the front end.
You’re the second person who has told me the front end ought to update real time if I’m using the Bubble db (which I am). No idea why I’m not seeing that behavior sometimes.
Same issue with me. I think more than half the time, the RG doesn’t update.
I haven’t waited long before forcing it with a page refresh.
Thinking out loud, I wonder if there’s a way to leverage the front-end “do every 5 seconds” workflow
Can you share your RG settings?
Do a search for Correspondence
Constraint
related_contact = CS contact id
(Custom state for current contact)
I also have a field that supposed to reflect a certain date in the database.
Parent group’s contact’s last_contacted_date
Neither gets updated sometimes.
To add to this, in my experiences, lists are reliably updated.
If you have an RG that is showing the contents of a list, it is reliably and instantly updated.
An RG that is showing the results of a search is not reliably updated.
What about a field?
To my recollection, field updates have always been reliable. Maybe that’s why list updates are reliable.
The problem is happening with a field as well.