Repeating Group is cooking itself with backend workflows

Need help
1

Hey everyone, I’m working on a Bubble app where I have a repeating group that displays a schedule (e.g., meetings). I’ve set up a “Sync” button that triggers a backend workflow, which fetches updated schedule data (including new, updated, or removed entries) and syncs it into the Bubble database.

The backend workflow works fine in terms of updating the data, but the repeating group doesn’t always reflect the changes immediately and users complain and sometimes keep refreshing once the cooldown finishes. Sometimes it updates right away, and other times I have to manually refresh the page to see the new data AND THAT SUCKS :frowning: PEOPLE GET MAD AT ME! . It seems inconsistent, possibly based on user load or caching or the repeating group just doesn’t want to update with the new db? In the repeating group there’s a number of lookups as well so it might struggle to get them all updated?

Is there a reliable way to force the repeating group to refresh from the database (not from local cache) once the backend workflow finishes or after a short delay?

Any best practices or workarounds to ensure the UI reflects the latest synced data would be much appreciated.

Thanks!

Any bubble brothers or sisters can help me with suggestions?

I can bet my left nut that @tylerboodman or @georgecollier have felt this and know the exact solutions :smiley: if they don’t then there’s probably no hope :frowning:

2

I would love get a piece of your left nut.

Let me see if I understand, the fetch call is to an external service, correct? My hunch is that this call is being cached by Bubble. I trip on this Bubble “feature” (air-quotes :roll_eyes: ) all the time. Add a nonce to force Bubble to actually make the call. A nonce can be :current date in iso...

Another thing to look at is your repeating group’s expression. Is the data type the same as the one you’re updating? Meaning, if the fetch writes to the data type available dates and the rg expression is also doing a search for available dates those should be updated right away. What might not be updating is if:

  • the fetch call is updating a different data type than the one of the rg
  • the rg’s data source is a state
  • an action is populating the rg
3

Hi!!
Try adding a short delay after the backend workflow, then refresh the repeating group’s data source or use a custom state to force update and avoid caching issues. I hope this might helpful for you..
Regards