Actions triggering full refresh of the CE Connect cache
Version:
There are some scenarios and actions that trigger a full refresh of the Commerce Engine Connect cache. Depending on the number of cached Commerce items, clearing the content of a cache can cause significant performance degradation on websites under heavy loads.
The following are common scenarios and actions that trigger a full refresh of the Commerce Engine Connect cache:
| Deployment topology | Scenario/triggering action | Note |
|---|---|---|
| Standalone, on-prem deployment | Add or modify one or multiple Commerce items. | Triggers incremental indexing and full refresh of Commerce cache. |
| Explicitly request a full rebuild of Catalog items index or a Commerce cache refresh. | For example, manual update of the Commerce cache and rebuild of the Sitecore Web index. | |
| Distributed Sitecore XC deployment | Add or modify more than 20 Commerce items. Note The quantity of new or updated items depends on configuration. | Triggers full re-indexing of catalog items if the number of new or modified items exceeds the value of the fullCacheRefreshThreshold property defined in the CE Connect caching configuration. |
| Explicitly request a full rebuild of Catalog items index or a Commerce cache refresh. | For example, manual update of the Commerce cache and rebuild of the Sitecore Web index. |
If you have suggestions for improving this article, let us know!