The refresh button should just be re-triggering the underlying query If you download the table data (from the table toolbar) when this happens, does it have the wrong data in the export as well?
I'm able to reproduce the bug, below I attached a exported app's JSON file. I think I found the issue: if the resource query return a new array order each time, the search will have this issue. In the demo app, I use _.shuffle to simulate this.
Seconding @hiep95 that this is a bug.
I have a Query JSON with SQL with WHERE filter values applied from other components like so. When a filter value changes, the resolved query body does too, it is run again and table refreshes, but the existing search term is not applied to the new resultset.
To @Tess point, Refresh only re-queries, it doesn't "refresh" the search.
Only way around: edit the search term and change e.g. last letter to itself. Changing programmatically doesn't work.
The fix should be to force reapplying the search term (fuzzy or not) after a refresh, triggered manually or automatically.