Answers.Body: <p>that notification_retry api isn't core - its an extension :-)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T02:49:32.703Z
Answers.LastActivityDate: 2015-08-06T02:49:32.703Z
Answers.UserDisplayName: eileen
Answers.Body: <p>Eileen,thanks, duly noted that it's an extension, not in core. Thanks for writing the extension! </p>
  
  <p>So to answer my own question -  </p>
  
  <p>drush cvapi NotificationLog.retry sequential=1 system_log_id=XXX </p>
  
  <p>will retry/rerun system_log entries as the previous </p>
  
  <p>drush cvapi notification_log.retry id=XXX</p>
  
  <p>did, and I have no reason to believe otherwise.   </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T10:56:39.207Z
Answers.Text: Yep - that's correct & the output that you saw is expected - whether or not it succeeds I guess .
  
  The extension is here https://github.com/eileenmcnaughton/nz.co.fuzion.notificationlog
  
  It currently only supports auhorize.net although the previous (fuzion repo) version also supported paypal, paybox & omnipay & there is not a lot of work to bring those back at some point
Answers.UserDisplayName: eileen
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T10:58:31.643Z
Answers.Text: (I mention all that extra detail for other people who might read it Joe )
Answers.UserDisplayName: eileen
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-07T17:55:56.903Z
Answers.Text: Eileen, thanks for all the extra detail - very useful
Answers.UserDisplayName: Joe McLaughlin
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-06T05:46:25.197Z
Answers.LastActivityDate: 2015-08-06T05:46:25.197Z
Answers.UserDisplayName: Joe McLaughlin
Body: <p>Trying to re-run/retry some 'stuck'/"pending" notifications in the system log using:</p>
  
  <p>drush cvapi NotificationLog.retry sequential=1 system_log_id=XXX</p>
  
  <p>but that just produces an array with the JSON data in the log entry. </p>
  
  <p>drush cvapi notification_log.retry id=748 used to do the trick. </p>
  
  <p>Any ideas? Thanks.  </p>
  
Tags: <api><contributions><authorize.net>
Title: What should drush cvapi NotificationLog.retry sequential=1 system_log_id=XXX do?
ThreadText: # What should drush cvapi NotificationLog.retry sequential=1 system_log_id=XXX do?
  
  (Asked by: username_0 on 2015-08-05)
  
  Trying to re-run/retry some 'stuck'/"pending" notifications in the system log using:
  
  drush cvapi NotificationLog.retry sequential=1 system\_log\_id=XXX
  
  but that just produces an array with the JSON data in the log entry.
  
  drush cvapi notification\_log.retry id=748 used to do the trick.
  
  Any ideas? Thanks.
  
  **Tags:** api, contributions, authorize.net
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-08-06. Score: 2 | Accepted answer
  
  that notification\_retry api isn't core - its an extension :-)
  
  
  ---
  
  ### Answer by username_0 on 2015-08-06. Score: 2
  
  username_1,thanks, duly noted that it's an extension, not in core. Thanks for writing the extension!
  
  So to answer my own question -
  
  drush cvapi NotificationLog.retry sequential=1 system\_log\_id=XXX
  
  will retry/rerun system\_log entries as the previous
  
  drush cvapi notification\_log.retry id=XXX
  
  did, and I have no reason to believe otherwise.
  
  > **Comments:**
  > **username_1**: Yep - that's correct & the output that you saw is expected - whether or not it succeeds I guess .  The extension is here https://github.com/eileenmcnaughton/nz.co.fuzion.notificationlog  It currently only supports auhorize.net although the previous (fuzion repo) version also supported paypal, paybox & omnipay & there is not a lot of work to bring those back at some point  
  > **username_1**: (I mention all that extra detail for other people who might read it Joe )  
  > **username_0**: username_1, thanks for all the extra detail - very useful  
  
  ---
  
  