As far as I understand how it works…
To start with, let’s separate screen refresh (which can happen only as a result of some action), and list contents refresh.
As I understand @creativechili is talking about refreshing the list contents, when the list is displaying external collection and some new data has been added / existing data altered.
I don’t think that such function exists in Adalo external collections. In order for an Adalo app to know that data in the external collection has been changed, there are 2 possible ways: either Adalo need to send a request to the collection, or collection needs to report the change.
First way may lead to high resource consumption (how often Adalo should send the request? Once per second? Once per 5 seconds? Once per minute? What about external collection API rate limits? What about network/server limits?).
Second way is better from performance point of view, but for this Adalo needs to have some “listener” which listen to the changes, and External collection needs to be able to send requests to this “listener”.
Long story short, based on what I see how External collections work, I don’t think that 2nd way is possible to implement universally for each possible type of collection.
But as I understand the original question was related to an issue something like that: when new data arrives to Xano or Airtable, or data is changed there, these changes need to be reflected in Adalo application with least possible delay and without user interaction.
As for me this could be done by “simulating” the 1st approach from above, i.e. re-sending the request to External Collection. May be this could be done via some tricks of hiding/showing the list (using couple of countdowns), or by sending a user to an empty screen and returning him/her back automatically (again, with countdown timer). These methods might initiate a “refresh” of the external collection list. Though as they are workarounds, they might not be very stable.
Just my 2 cents to share some thoughts.
Best regards, Victor.