CiviCRM Community Forums (archive)

Have you checked if the ones that haven't updated have the status override box ticked with status New having been set manually?  The Update Membership Statuses job does not update memberships with the status override flag set.

With your current settings someone who had been a member in the past and rejoined after being lapsed for more than 3 months would get the status "active".  It is possible that staff have decided that person should actually have the status 'new' and have used status override to set it manually.

You shouldn't update the statuses via SQL, you should untick the status override box so that the system can set the status correctly.

If you have updated the statuses via SQL and left the status override box ticked you are just perpetuating the problem.  When the status should change from active to expired, or from expired to new if someone rejoins, then this won't happen if the status override box is ticked.

You say

But a lot of membership with status "new" don't update...

You need to work out why your staff think they need to manually set the the status to new and work to solve that problem. The status override box would usually only be ticked to let staff manually select one of the statuses that aren't part of the normal membership life cycle eg "cancelled".

Perhaps you need to change the  parameters for membership status "new" to: start : start date / end : start date 3 months