Answers.Body: <p>I think the issue is similar to what Parvez describes with a slight twist. I think it is the fact that you renamed Expired to be Lapsed, and the system is set up so that once it is Expired it will not progress based on the rules.</p>
  <p>So if you create a new Lapsed one, or switch your Lapsed and Not Renewed around you might find it starts working.</p>
  <p>I.e. the original 'expired' has special properties and hence should be the last one in the automated statuses.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-08T15:51:07.793Z
Answers.Text: Good catch Pete, that may well be the issue - all I know is theres a lot of hidden features regards expired/non current members!
Answers.UserDisplayName: Parvez Saleh
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-08T16:21:52.440Z
Answers.Text: Thank you both so much. Swapping them around appears to have sorted it for us :-)
  Will see what happens in January when 'grace' & 'lapsed' come back into play!
Answers.UserDisplayName: astroned
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-07T19:59:08.293Z
Answers.LastActivityDate: 2020-12-08T18:27:03.717Z
Answers.LastEditDate: 2020-12-08T18:27:03.717Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>Sorry I thought I'd answered previously but I'm 99% this is down to the fact that once a membership status becomes ended the automated rules then wont touch it. So the first status of type ended in theory would be the one that gets applied and any subsequent ones wouldn't be something that automatically gets moved on. I'm 99% thats the issue your facing, a previous question asked if CiviRules could be used to change membership statuses (which it cant yet), your case is probably one that fits a CiviRules status change I think. Let me know if you prove the theory!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-07T15:41:29.940Z
Answers.Text: Thanks Parvez. What do you mean by 'becomes ended'?  Both grace and lapsed are current memberships, 'not renewed' is the first status that we have configured to not be current.
Answers.UserDisplayName: astroned
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-07T16:15:01.953Z
Answers.Text: Each status has a "Member" flag of yes or no. I think the first status with a "No" is the one that will get set. When CiviCRM then re-runs its status rules it excludes any that are "No" type membership statuses (I think) and therefore your members never move onto other statuses. Like I say its a theory but I know that CiviCRM often excludes lapsed members from processes and I'm pretty sure thats the reason.
Answers.UserDisplayName: Parvez Saleh
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-07T15:26:45.800Z
Answers.LastActivityDate: 2020-12-07T15:26:45.800Z
Answers.UserDisplayName: Parvez Saleh
Body: <p>This is a follow-up from a previous question that we couldn't find a resolution for (<a href="https://civicrm.stackexchange.com/questions/35319/membership-status-rules-not-updating-statuses?noredirect=1#comment40847_35319">Membership status rules not updating statuses</a>).</p>
  <p>We have three status rules once a membership has not been renewed - Grace, Lapsed and Not Renewed. 'Not Renewed' is an extension of Lapsed and we consider it more permanent than lapsed and cannot target those members again unless they get in touch due to data protection/spam etc.</p>
  <p>The issue was that membership status of those members more than 3 months past end date did not get updated to 'Not renewed' and stayed at lapsed.  Thought this was maybe just a limitation of the number of 'lasped' membership status you could have.  However, checking today, I see a small number of membership statuses have updated to 'not renewed'. In all cases, there was a failed PayPal transaction so the contribution is still pending.</p>
  <p>Able to add pictures of the rules this time for clarity. Anyone have any ideas what we're doing wrong?</p>
  <p>Thanks for your time :-)</p>
  <p><a href="https://i.sstatic.net/MVthS.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/MVthS.png" alt="enter image description here" /></a></p>
  <p><a href="https://i.sstatic.net/hWXdy.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/hWXdy.png" alt="enter image description here" /></a></p>
  <p><a href="https://i.sstatic.net/tWLRz.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/tWLRz.png" alt="enter image description here" /></a></p>
  <p><a href="https://i.sstatic.net/NGOUo.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/NGOUo.png" alt="enter image description here" /></a></p>
  
Tags: <civimember>
Title: Membership status rules query
ThreadText: # Membership status rules query
  
  (Asked by: username_0 on 2020-12-07)
  
  This is a follow-up from a previous question that we couldn't find a resolution for ([Membership status rules not updating statuses](https://civicrm.stackexchange.com/questions/35319/membership-status-rules-not-updating-statuses?noredirect=1#comment40847_35319)).
  
  We have three status rules once a membership has not been renewed - Grace, Lapsed and Not Renewed. 'Not Renewed' is an extension of Lapsed and we consider it more permanent than lapsed and cannot target those members again unless they get in touch due to data protection/spam etc.
  
  The issue was that membership status of those members more than 3 months past end date did not get updated to 'Not renewed' and stayed at lapsed. Thought this was maybe just a limitation of the number of 'lasped' membership status you could have. However, checking today, I see a small number of membership statuses have updated to 'not renewed'. In all cases, there was a failed PayPal transaction so the contribution is still pending.
  
  Able to add pictures of the rules this time for clarity. Anyone have any ideas what we're doing wrong?
  
  Thanks for your time :-)
  
  [![enter image description here](https://i.sstatic.net/MVthS.png)](https://i.sstatic.net/MVthS.png)
  
  [![enter image description here](https://i.sstatic.net/hWXdy.png)](https://i.sstatic.net/hWXdy.png)
  
  [![enter image description here](https://i.sstatic.net/tWLRz.png)](https://i.sstatic.net/tWLRz.png)
  
  [![enter image description here](https://i.sstatic.net/NGOUo.png)](https://i.sstatic.net/NGOUo.png)
  
  **Tags:** civimember
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2020-12-07. Score: 1 | Accepted answer
  
  I think the issue is similar to what Parvez describes with a slight twist. I think it is the fact that you renamed Expired to be Lapsed, and the system is set up so that once it is Expired it will not progress based on the rules.
  
  So if you create a new Lapsed one, or switch your Lapsed and Not Renewed around you might find it starts working.
  
  I.e. the original 'expired' has special properties and hence should be the last one in the automated statuses.
  
  > **Comments:**
  > **username_2**: Good catch Pete, that may well be the issue - all I know is theres a lot of hidden features regards expired/non current members!  
  > **username_0**: Thank you both so much. Swapping them around appears to have sorted it for us :-) Will see what happens in January when 'grace' & 'lapsed' come back into play!  
  
  ---
  
  ### Answer by username_2 on 2020-12-07. Score: 2
  
  Sorry I thought I'd answered previously but I'm 99% this is down to the fact that once a membership status becomes ended the automated rules then wont touch it. So the first status of type ended in theory would be the one that gets applied and any subsequent ones wouldn't be something that automatically gets moved on. I'm 99% thats the issue your facing, a previous question asked if CiviRules could be used to change membership statuses (which it cant yet), your case is probably one that fits a CiviRules status change I think. Let me know if you prove the theory!
  
  > **Comments:**
  > **username_0**: Thanks Parvez. What do you mean by 'becomes ended'?  Both grace and lapsed are current memberships, 'not renewed' is the first status that we have configured to not be current.  
  > **username_2**: Each status has a "Member" flag of yes or no. I think the first status with a "No" is the one that will get set. When CiviCRM then re-runs its status rules it excludes any that are "No" type membership statuses (I think) and therefore your members never move onto other statuses. Like I say its a theory but I know that CiviCRM often excludes lapsed members from processes and I'm pretty sure thats the reason.  
  
  ---
  
  