Dataverse WebAPI slow response caused by cache?

(0) Share

Report

Posted on by JBC777

I have a question about the WebAPI and slow access to data already in dataverse.

I have JS functionality that uploads a file from the page, to azure and stores the meta data in Dataverse. all working.

flow is:

1. JS uploads conent to Azure, does some processing and checking and then updates a dataverse table. Working

2. i then check the Model Admin app, and i can see the file registered correctly. All good

3. Its taking at least 5 mins for the content to appear in power pages via the webAPI. it does appear, its just very slow.

i have all the user warnings and auto refresh but wanted to know if anyone has any ideas how to bypass what i assume is a cache?

i have seen that there are 'moans' about this for years so don't have high hopes but worth a try.

Categories:

Customize & extend

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @JBC777,

This delay is caused by Power Pages server‑side caching, not Dataverse. Dataverse updates instantly, but anything rendered through Liquid/Entity Lists can lag ~5 minutes due to aggressive caching.

https://community.powerplatform.com/forums/thread/details/?threadid=70bda703-ce64-f011-bec2-7c1e520b3d67

https://learn.microsoft.com/en-us/power-pages/admin/clear-server-side-cache

Fast ways to fix it:

Bypass Liquid → Read data using Portals Web API (/_api) from JavaScript. This returns live data and avoids the cache entirely.
If you must use Liquid, add a cache‑buster (e.g., a now condition) to force a fresh fetch.
As a fallback, you can manually clear cache in Admin Center / /_services/about.

Best practice: For real‑time scenarios, always fetch data via /_api instead of Liquid.

References:
https://powerlogichub.com/power-pages-dataverse-web-api-caching-fix/
https://community.powerplatform.com/forums/thread/details/?threadid=70bda703-ce64-f011-bec2-7c1e520b3d67
https://rishandigital.com/power-pages/managing-portal-cache-and-refresh/

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No
Suggested answer

Lucas001 2,567 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @JBC777,

as mentioned in the reply above this is one way doing it.

You can also force a liquid refresh. @oliver.rodrigues has a great post about it which I tend linking for these cases: https://oliverrodrigues365.com/category/power-apps-portals/caching/

If one or the other answer provides sufficient information please accept one as answer.

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 381 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @JBC777,

For Power pages caching refresh refer these articles. I'm sure these would be helpful:

1. How server-side caching works in Power Pages | Microsoft Learn

2. Managing portal cache and refresh – Rishan Solutions

I hope this would solve your problem.

Happy to help!

Was this reply helpful? Yes No
JBC777 83 on at

Like
a
(0)

Report
Copy link

Link copied!

thanks for the clarification on my wording. its the cache at Power Pages side not dataverse.

Thanks for the answers. I am calling the WebAPI direct from Javascript and there is still a delay, so liquid i don't think is involved.

I am going to try and add a timestamp to the query and see if that helps.

Was this reply helpful? Yes No
Suggested answer

Fubar 8,512 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

FYI

The Power Pages WebAPI also makes use of the Power Pages Cache, so just calling it may not pull data direct from dataverse that is not already in the cache (particularly if the same query has been run previously).

As per several of the links already provided in other posts the way to work around the cache is to make your query relatively unique e.g. add a condition to the query that is always true but that contains value that is relatively unique such as Created On is less than today (formatted down to seconds). The system then says I don't recognise that query (as its not been used before) I need to pull the data for it direct from Dataverse. This approach works for both the Portals WebAPI and also if you use Liquid fetchxml (but you don't have the ability to do it for standard lists and subgrids).

For creates/updates that are not direct from the portal (e.g. update to dataverse from another interface e.g. Model Driven app or another API) data is usually pushed to cache within a minute or two, but Microsofts SLA for it is 15 minutes.

Was this reply helpful? Yes No