When using Personal Catalog Views there is a period of time between when a customer is in one category and a change on their record puts them in another category. Does anybody know why the delay, is it caching or indexing that happens of the customers or items? Also if somebody knows how often this occurs and if there is a way to trigger it when we know a change has happened on a record? Reason for the question is that we have a specific PCV to lock customers from ordering if they are overdue on payments or they haven't submitted certain records after a deadline. Unfortunately we are finding that this can exceed 1.5 hours and we want to get a better idea of the mechanisms and whether we need to swap away from using PCV's for this particular disabling. The delay also occurs in the opposite direction, like if they made a payment or submitted records there is a long delay before they can order.

If the customer segments are dynamic (ie generated by a saved search) then the entity groups are cached for performance reasons. The cached entity groups should only last for one hour.

Thanks that makes sense. We do use dynamic ones. We did have a case where it took more than 1.5 hours, but it was also in sandbox so maybe caching is longer in sandbox?

I don't have any extra information about sandbox. I would have thought it would be the same code