Answers.Body: <p>Change the date for the next scheduled recurrence.
  Table civicrm_contribution_recur > Column next_sched_contribution_date</p>
  
  <p>Change it to today and run your cron job or change it to tomorrow and it should process them with tomorrows transactions.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-05T04:33:40.930Z
Answers.Text: That’s correct; if you have lots - use mysql to set all next scheduled dates of e.g. series with status in progress and next scheduled date in the past to tomorrow; if you need a user GUI -> use Views Bulk Operations with CiviCRM Entity
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-08T22:25:59.087Z
Answers.Text: Worthwhile note: be sure to note the next_sched_contribution_date value before changing it, and adjust afterward, if necessary, to an appropriate day-of-month.
Answers.UserDisplayName: TwoMice
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-12T16:00:37.130Z
Answers.Text: Check out this: https://github.com/iATSPayments/com.iatspayments.civicrm/wiki/Recurring-Contribution-Failure-Handling
  Short answer: if it was only a few days, then it might have been handled automatically. You can configure some aspects of how the extension handles failed recurring contributions, and getting email alerts about them might be a good idea in your case.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-04T22:54:20.817Z
Answers.LastActivityDate: 2018-01-04T22:54:20.817Z
Answers.UserDisplayName: Iowa Boy
Body: <p>iATS credentials were messed up for a couple of days in December, and now I have lots of recurring contributions that failed, with source="iATS Payments Recurring Contribution (id=N) Agent code has not been set up on the authorization system. Please call iATS at 1-888-955-5455." </p>
  
  <p>Is there a way to re-run those recurring contributions?</p>
  
Tags: <contributions><recurring-contributions><iats>
Title: Re-run iATS recurring contributions that failed due to bad iATS account credentials?
ThreadText: # Re-run iATS recurring contributions that failed due to bad iATS account credentials?
  
  (Asked by: username_0 on 2018-01-04)
  
  iATS credentials were messed up for a couple of days in December, and now I have lots of recurring contributions that failed, with source="iATS Payments Recurring Contribution (id=N) Agent code has not been set up on the authorization system. Please call iATS at 1-888-955-5455."
  
  Is there a way to re-run those recurring contributions?
  
  **Tags:** contributions, recurring-contributions, iats
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-01-04. Score: 3 | Accepted answer
  
  Change the date for the next scheduled recurrence.
  Table civicrm\_contribution\_recur > Column next\_sched\_contribution\_date
  
  Change it to today and run your cron job or change it to tomorrow and it should process them with tomorrows transactions.
  
  > **Comments:**
  > **username_2**: That’s correct; if you have lots - use mysql to set all next scheduled dates of e.g. series with status in progress and next scheduled date in the past to tomorrow; if you need a user GUI -> use Views Bulk Operations with CiviCRM Entity  
  > **username_0**: Worthwhile note: be sure to note the next_sched_contribution_date value before changing it, and adjust afterward, if necessary, to an appropriate day-of-month.  
  > **username_3**: Check out this: https://github.com/iATSPayments/com.iatspayments.civicrm/wiki/Recurring-Contribution-Failure-Handling Short answer: if it was only a few days, then it might have been handled automatically. You can configure some aspects of how the extension handles failed recurring contributions, and getting email alerts about them might be a good idea in your case.  
  
  ---
  
  