Steps to reproduce:
-
When the page loads, the user makes a dropdown selection that triggers a workflow which updates CustomState1 based on a search of Table1.
-
A button triggers another workflow that makes changes to records in Table1 — the same table that CustomState1 pulls from.
-
In that button workflow, I included an action that reassigns CustomState1 using the exact same search as in step 1. (Copied and pasted the action, no differences.)
-
After this runs, CustomState1 now shows fewer records — e.g., 159 instead of 163 after modifying four records.
-
However, if I manually refresh the page, CustomState1 repopulates with the correct total (163).
What I’ve tried:
-
Emptying the state first, then resetting it.
-
Sorting by Modified Date or Created Date.
-
Adding a short pause before the reset.
-
Ensuring I’m not using
:unique elementsor client-side filters.
None of these change the outcome — the list in the custom state only becomes accurate after a full page reload.
Has anyone seen this before? It seems like Bubble is caching the old client-side list and not re-pulling the updated records, even when I explicitly run a new “Set state” with the same search.
Goal:
Force the custom state to reflect the freshly updated records from the database without needing to refresh the page.