Yes but you’re accruing WUs. To do it client side you can refresh after each update and pull changes from other users by polling every 10, 20, 30 seconds etc
Yea I’m just saying some ppl have a workaround to simulate a realtime database. I mean honestly how bad could the WUs be if users searched a 1 item count table 
You’d be calling backend workflows repetitively with no control over how often, for every user, for every update. Regardless of the data you’re returning. That method might have worked before but under the new WU pricing, it could end being very expensive very quickly.
what does “refresh data source” mean in bubble terms?
Refreshing the data means calling the Xano endpoint (through the plugin) again to get up to date data.
In Bubble there’s no direct equivalent as Bubble pushes changes to the client via web sockets. I suppose if you had the data source eg of a repeating group linked to a custom state list. In a workflow, empty the value of the custom state and then in another step do another search and assign it to the custom state list. This will “refresh” the data but it’s not necessary.
If you’ve only ever used Bubble’s database, the realtime might seem the norm but it isn’t in the wider database world. It’s used where it brings the most benefit eg chat, dashboards etc and you should use it where necessary but it’s too resource intensive to use it everywhere, yet Bubble forces it’s use for everything. That’s now gonna cost you.
Could you share which tools those are that expose the inefficiencies?