Delay for updating changes to datasource

[vickywhitmore]

I am getting the same issue.  I have put the refresh command multiple places in the app to try and force a refresh as I need to get the new data to display straight away.  For testing going into task manager to restart the service is fine, but using it for production wouldn't work as I would need to be refreshing it every two seconds as users are trying to use the app.  Has anyone else found a solution to get it to refresh quickly? 

[jont22]

I haven’t noticed issues with refresh in production. Only during development. I am still having the issue though.

[walegado]

Yes.  Go to Services where your On-premises data gateway is installed. 

Find the On-premises data gateway on the list of services and do a re-start.

Refresh the connection in PowerApps and you'll see the changes.

[Francis_Ayson]

I am also experiencing the same issue. I refreshed DataSource, Reconnected my SQL Server, cleared my browsing history, and yet i still get the same problem on the delay for updating changes in Datasource. It should not be as difficult as this when refreshing sql database via powerapps otherwise we will be experiencing delays in developing the app as well since we could not find the new column we have added in the datasource. 

[kevinsray]

I am also seeing this issue recently.

Whilst restarting the gateway service seems to fix the problem, it shouldn`t be required.
This is an issue which never used to happen.

Would be really nice if MS could let us know why this is now happening and how they intend on fixing the issue.

I am sure a lot of people wouldn`t be happy with having to restart a service which is running in production.

[fugixi]

I can confirm that this problem occurs for other data sources as well.

I currently have a large SharePoint (containing around 13 000 items).

My first thought was that there was a delay when refreshing the data source, but the issue seems to rather be with the actual ClearCollect function, which needs to be performed multiple times.

This most certainly has to be a bug.