Body: <p>It seems that a newly created group (with mailinglist checked) isn't directly available when sending a new mass mailing, but does eventually end up being visible after a few minutes (probably between 5 and 10 min?)</p>
  
  <p>This happen with the "new" angular interface, we didn't have this issue with the previous interface.</p>
  
  <p>Are the list of available groups cached somewhere? Is there a way to clear that cache (or submit a PR so it does it by default after creating a mailing list group)?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-22T12:37:34.030Z
Comments.Text: I just tried this on [dmaster](http://dmaster.demo.civicrm.org/) and the group was directly available within next load of New Mailing Page after creating the group. I don't think it may be a cache issue as the group list are retrieved by calling the group `get` api.
Comments.UserDisplayName: jitendra - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-22T12:48:16.243Z
Comments.Text: Ahh, thanks, I wonder what in my config makes it cached for a while.
Comments.UserDisplayName: Xavier
Tags: <civimail>
Title: How to make new groups immediately visible in a new mailing?
ThreadText: # How to make new groups immediately visible in a new mailing?
  
  (Asked by: username_0 on 2016-01-22)
  
  It seems that a newly created group (with mailinglist checked) isn't directly available when sending a new mass mailing, but does eventually end up being visible after a few minutes (probably between 5 and 10 min?)
  
  This happen with the "new" angular interface, we didn't have this issue with the previous interface.
  
  Are the list of available groups cached somewhere? Is there a way to clear that cache (or submit a PR so it does it by default after creating a mailing list group)?
  
  **Tags:** civimail
  
  > **Comments:**
  > **username_1**: I just tried this on [dmaster](http://dmaster.demo.civicrm.org/) and the group was directly available within next load of New Mailing Page after creating the group. I don't think it may be a cache issue as the group list are retrieved by calling the group `get` api.  
  > **username_0**: Ahh, thanks, I wonder what in my config makes it cached for a while.  
  
  ---
  
  ## 0 answers
  
  