Answers.Body: <p>The first one, <em>process_membership</em>, goes around and updates the membership statuses.  It's what sets a member's status to "expired" once the end date comes around.  Once upon a time, it sent reminders, but it doesn't anymore (new installations don't have that label for the job).  You should be able to have it run daily.</p>
  
  <p>The second one, <em>send_reminder</em>, is for all reminders--activity, event, birthday, etc. in addition to memberships.  Although you could get away with running it daily, you should run this hourly, because you may have time-sensitive reminders set up for events.</p>
  
  <p>Once you have the job running, you should go into the Scheduled Reminders admin page and set up the appropriate reminders.</p>
  
  <p>The third one, <em>process_membership_reminder_date</em>, should stay disabled--it's obsolete, as the warning says.  You could even delete it if you like.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T12:02:41.903Z
Answers.Text: wtf .. i was going to delete process_membership_reminder_date .. but its gone today. and the label for process_membership has changed. I had to come back here to see what I wrote yesterday. hm, whatever happened, i suppose its good.
Answers.UserDisplayName: commonpike
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-27T16:03:14.807Z
Answers.LastActivityDate: 2015-05-27T16:03:14.807Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I want to send out membership reminders 6 weeks, 3 weeks, etcetera before membership lapses. To send them out, i see multiple cron jobs:</p>
  
  <ul>
  <li>process_membership, named Update Membership Statuses and Send Renewal
  Reminders  </li>
  <li>send_reminder, named Send Scheduled Reminders, and </li>
  <li>process_membership_reminder_date, named Set Renewal Reminder Dates</li>
  </ul>
  
  <p>The first one should be on, I guess, like daily or so ?
  It may depend on the second one - not sure ?
  The 3rd one comes with a warning that it should be off:</p>
  
  <pre><code>WARNING: Membership renewal reminders have been migrated to the Schedule Reminders functionality
  </code></pre>
  
  <p>indicating that perhaps the first one doesnt have to be on at all.</p>
  
  <p>I'm all confused :-) How do I set this up ?</p>
  
Tags: <civimember><cron-job><scheduled-reminders>
Title: cron jobs process_membership, send_reminder and process_membership_reminder_date
ThreadText: # cron jobs process_membership, send_reminder and process_membership_reminder_date
  
  (Asked by: username_0 on 2015-05-27)
  
  I want to send out membership reminders 6 weeks, 3 weeks, etcetera before membership lapses. To send them out, i see multiple cron jobs:
  
  * process\_membership, named Update Membership Statuses and Send Renewal
    Reminders
  * send\_reminder, named Send Scheduled Reminders, and
  * process\_membership\_reminder\_date, named Set Renewal Reminder Dates
  
  The first one should be on, I guess, like daily or so ?
  It may depend on the second one - not sure ?
  The 3rd one comes with a warning that it should be off:
  
  ```
  WARNING: Membership renewal reminders have been migrated to the Schedule Reminders functionality
  
  ```
  
  indicating that perhaps the first one doesnt have to be on at all.
  
  I'm all confused :-) How do I set this up ?
  
  **Tags:** civimember, cron-job, scheduled-reminders
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-05-27. Score: 3 | Accepted answer
  
  The first one, *process\_membership*, goes around and updates the membership statuses. It's what sets a member's status to "expired" once the end date comes around. Once upon a time, it sent reminders, but it doesn't anymore (new installations don't have that label for the job). You should be able to have it run daily.
  
  The second one, *send\_reminder*, is for all reminders--activity, event, birthday, etc. in addition to memberships. Although you could get away with running it daily, you should run this hourly, because you may have time-sensitive reminders set up for events.
  
  Once you have the job running, you should go into the Scheduled Reminders admin page and set up the appropriate reminders.
  
  The third one, *process\_membership\_reminder\_date*, should stay disabled--it's obsolete, as the warning says. You could even delete it if you like.
  
  > **Comments:**
  > **username_0**: wtf .. i was going to delete process_membership_reminder_date .. but its gone today. and the label for process_membership has changed. I had to come back here to see what I wrote yesterday. hm, whatever happened, i suppose its good.  
  
  ---
  
  