When a merchandiser saves an individual category on the Tagalys dashboard, we trigger a process to update and clear the cache right away for the category ID. These merchandising updates will usually be live in the front end within a minute. Actions that cause changes to multiple categories (like boosting, product sync or t-score updates) save the affected category ids to a queue and the queue is processed at a rate that is configurable per client.
How does Tagalys bust the cache to update product positions during merchandising? Print
Created by: Syrah K
Modified on: Mon, 11 Nov, 2019 at 3:14 AM
Did you find it helpful?Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.