CiviCRM Community Forums (archive)

Hi Lianne - We do "cache" the Smart Group members in order to prevent running the query every time a page loads. However the "existing records" which match a Smart Group query should get put in the cache when the Smart Group is created or modified AND the cache should be updated appropriately when a record is changed such that it now matches the query.

It's possible that there are some record  update operations that are not appropriately updating the cache. In order for us to track this down we'll need you to:
1. Describe and / or provide screen shot of the smart group search criteria
2. List the steps you've taken to produce the situation where a record SHOULD be in the smart group but isn't showing up there.

(If you can recreate this on the public demo and list the steps - that's ideal.)

I wonder if it would be useful to have some additional functionality whereby you could ask the database to search through existing records that have been given the criteria of the smart group and have the smart group updated?

This should be happening now. As I mentioned above, if you can describe in detail a set of steps where it does NOT happen - and you or we can reproduce it , then that's a bug to be fixed.

I just ran a quick test on my local sandbox, and updating a participant status via Edit Participant definitely added them to a smart group which was based on that participant status (I created a smart group for all "Cancelled" participants).

If you tried to recreate using exact same steps on public demo and it didn't recreate, then possibly this is something fixed in latest stable release (3.0.3) - altho I didn't see an issue on that in the 3.0.3 issue queue :-(

Other suggestion is to examine what's happening "under the covers" a bit on your site. Smart group members are cached in civicrm_group_contact_cache. You can empty that table and then force it to re-populate by editing a Participant record and saving. You may need to run your advanced search again after that to make sure the cache is reloaded. So you can monitor what's happening in that table based on actions taken (e.g. add new participant) - and possibly uncover an insert that we're not trapping properly for addition to cache ??