Body: <p>I had a reminder set up that simply sent an email to people on a given date who registered for a forthcoming event using the 'pay later' option, reminding them that they need to pay. All good.</p>
  
  <p>I then wanted to change the reminder so that it repeated every two weeks after that given date until two weeks after the event start date. But CiviCRM won't let me set a repeating pattern for a reminder that uses an absolute data. Or rather it does let me set up the repeating pattern, but then simply doesn't save that edit.</p>
  
  <p>I can't see any good reason why I might not be able to set up a reminder that sends an email on (for example) the 1st of January, and repeats every two weeks until an event start date. </p>
  
  <p>Which leads me to think that this is a bug. I've tested it on my live site (WP and Civi 4.6.21) and on <a href="http://wpmaster.demo.civicrm.org" rel="nofollow noreferrer">http://wpmaster.demo.civicrm.org</a></p>
  
  <p>The documentation for 4.7 (<a href="https://docs.civicrm.org/user/en/stable/email/scheduled-reminders/" rel="nofollow noreferrer">https://docs.civicrm.org/user/en/stable/email/scheduled-reminders/</a>) makes no mention, which further makes me think this is a bug:</p>
  
  <blockquote>
    <p>Choose when to send the reminder. This can be a set date or an amount of time before or after the start or end of your chosen entity.
    Check the Repeat box if you want to send this reminder more than once to the same group of people. This gives you choices about the interval of repetition and when the repetition should end.</p>
  </blockquote>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-11-17T15:28:09.557Z
Comments.Text: Noticing the same. I just want to set up a repeating reminder to a smart group starting from now. I can set a date fill out the repeating pattern, save but then the repeat information is lost.
Comments.UserDisplayName: Tenz
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-03T12:47:13.637Z
Comments.Text: FYI, this feature will be added in 4.7.19 -- see https://issues.civicrm.org/jira/browse/CRM-19663
Comments.UserDisplayName: lcdservices
Tags: <scheduled-reminders>
Title: Why can't I set up a repeating scheduled reminder with an absolute date?
ThreadText: # Why can't I set up a repeating scheduled reminder with an absolute date?
  
  (Asked by: username_0 on 2016-11-09)
  
  I had a reminder set up that simply sent an email to people on a given date who registered for a forthcoming event using the 'pay later' option, reminding them that they need to pay. All good.
  
  I then wanted to change the reminder so that it repeated every two weeks after that given date until two weeks after the event start date. But CiviCRM won't let me set a repeating pattern for a reminder that uses an absolute data. Or rather it does let me set up the repeating pattern, but then simply doesn't save that edit.
  
  I can't see any good reason why I might not be able to set up a reminder that sends an email on (for example) the 1st of January, and repeats every two weeks until an event start date.
  
  Which leads me to think that this is a bug. I've tested it on my live site (WP and Civi 4.6.21) and on <http://wpmaster.demo.civicrm.org>
  
  The documentation for 4.7 (<https://docs.civicrm.org/user/en/stable/email/scheduled-reminders/>) makes no mention, which further makes me think this is a bug:
  
  > Choose when to send the reminder. This can be a set date or an amount of time before or after the start or end of your chosen entity.
  > Check the Repeat box if you want to send this reminder more than once to the same group of people. This gives you choices about the interval of repetition and when the repetition should end.
  
  **Tags:** scheduled-reminders
  
  > **Comments:**
  > **username_1**: Noticing the same. I just want to set up a repeating reminder to a smart group starting from now. I can set a date fill out the repeating pattern, save but then the repeat information is lost.  
  > **username_2**: FYI, this feature will be added in 4.7.19 -- see https://issues.civicrm.org/jira/browse/CRM-19663  
  
  ---
  
  ## 0 answers
  
  