Answers.Body: <p>Info on sent reminders is stored in civicrm_action_log table.</p>
  
  <p><a href="https://issues.civicrm.org/jira/browse/CRM-15728" rel="noreferrer">https://issues.civicrm.org/jira/browse/CRM-15728</a> may help you understand how it works. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-15T07:15:16.220Z
Answers.LastActivityDate: 2015-05-15T07:15:16.220Z
Answers.UserDisplayName: JoAnne
Answers.Body: <p>While this may be an obstacle for you right now, the fact that the scheduled reminders system doesn't send out reminders after the first one is definitely a good thing.  If you have the job for sending scheduled reminders set to hourly (my preferred method, since it avoids the possibility that reminders only ever go out late at night, making them unreliable for reminding someone about something tomorrow), you don't want everyone to get a reminder every hour.</p>
  
  <p>If you want to remind someone multiple times per activity, you have two options:</p>
  
  <ul>
  <li>If you want the same message to go out, and the interval should be the same (every couple of days or something), enable repetition.</li>
  <li>If you want to vary the message or have a custom schedule (one month out, one week out, and then one day before, for example), just set up multiple reminders.  The system limits the reminders to once <em>per reminder</em> so other reminders set for the same activity won't interfere with each other.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-15T15:42:16.217Z
Answers.Text: Its a good thing - I agree!  Its also not explicit in the documentation that this is what happens, so I like to look in the database to understand how its preventing a send (and deleting the action_log entry makes testing iterations easier).
Answers.UserDisplayName: Eliot Mason
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-15T13:31:52.777Z
Answers.LastActivityDate: 2015-05-15T13:31:52.777Z
Answers.UserDisplayName: Andie Hunt
Body: <p>CiviCRM can send reminders for memberships, activities, etc.  I noticed that if I create an activity and send a reminder email (by forcing the scheduled job to run) that the activity won't generate another email even if the parameters (within 0 hours of completion) are still valid.</p>
  
  <p>Where/How does CiviCRM track a sent reminder so it doesn't send another?</p>
  
Tags: <scheduled-reminders>
Title: Where/How does CiviCRM track sent reminder notices?
ThreadText: # Where/How does CiviCRM track sent reminder notices?
  
  (Asked by: username_0 on 2015-05-15)
  
  CiviCRM can send reminders for memberships, activities, etc. I noticed that if I create an activity and send a reminder email (by forcing the scheduled job to run) that the activity won't generate another email even if the parameters (within 0 hours of completion) are still valid.
  
  Where/How does CiviCRM track a sent reminder so it doesn't send another?
  
  **Tags:** scheduled-reminders
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-05-15. Score: 5
  
  Info on sent reminders is stored in civicrm\_action\_log table.
  
  <https://issues.civicrm.org/jira/browse/CRM-15728> may help you understand how it works.
  
  
  ---
  
  ### Answer by username_2 on 2015-05-15. Score: 2
  
  While this may be an obstacle for you right now, the fact that the scheduled reminders system doesn't send out reminders after the first one is definitely a good thing. If you have the job for sending scheduled reminders set to hourly (my preferred method, since it avoids the possibility that reminders only ever go out late at night, making them unreliable for reminding someone about something tomorrow), you don't want everyone to get a reminder every hour.
  
  If you want to remind someone multiple times per activity, you have two options:
  
  * If you want the same message to go out, and the interval should be the same (every couple of days or something), enable repetition.
  * If you want to vary the message or have a custom schedule (one month out, one week out, and then one day before, for example), just set up multiple reminders. The system limits the reminders to once *per reminder* so other reminders set for the same activity won't interfere with each other.
  
  > **Comments:**
  > **username_0**: Its a good thing - I agree!  Its also not explicit in the documentation that this is what happens, so I like to look in the database to understand how its preventing a send (and deleting the action_log entry makes testing iterations easier).  
  
  ---
  
  