As a part of July release (version 9.2.6.x), we’re improving portal caching infrastructure to increase consistency and reliability.

Note

• No change to SLA for cache refresh (data transfer between Common Data Service and portal). Common Data Service record updates will reflect in Power Apps portals in 15 minutes.
• Data changes done using portals will reflect immediately in Common Data Service and portals.
• No change to clear server-side cache functionality. You can continue to use this functionality to clear server cache immediately.

Upcoming Changes

With changes in this release, we’re unifying caching approach for capacity-based portals and add-on portals.

 

What will change for different types of portals?

Capacity-based portal changes

After changes in this release, you won’t have to manually clear configuration entity cache for capacity-based portals.

Add-on portal changes

High load portals should see improved performance and a reliable data cache refresh.

 

FAQ:

Can I change the cache refresh duration from 15 minutes to a lesser duration?

No. SLA for cache refresh remains 15 minutes. Any changes from Common Data Service will reflect on portals within 15 minutes.

I’m using plugins or workflows to update data in other entities and need these data changes to reflect immediately on my portal.

This design approach isn’t recommended. Except the primary record where the create or update action is triggered, data reflection from Common data Service to portals is never guaranteed to be immediate.

Is there any difference in caching between capacity-based portals and add-on portals?

No.

How long does it take for changes to reflect from portals to Common Data Service?

Immediately, as long as the update changes a primary record and isn’t based on indirect changes to data using plugins or workflows.

 

See documentation here for detail.