Since the 9/16 code update, the new test order I set up on a one-day recurrence did not trigger after the designated time period.
The previous commit did trigger the renewal and thereby created the new order, so it seems something became undone.

Comments

vitis’s picture

vitis commented

subscribing

chadwick wood’s picture

chadwick wood commented

I think this was fixed in the 9/17 update. Look at the latest responses on this issue? #580226: Order status updates inconsistent

bearstar’s picture

bearstar commented

Thanks...and there might have been cron issues on the server....I have grabbed the latest version and will see if it behaves better.

univate’s picture

univate commented

No #580226: Order status updates inconsistent is unrelated to actual order renewals. That issue was about the order status that occur when a renewal occurs and allowing the order renewal to trigger other events like role renewals.

bearstar’s picture

bearstar commented

This was a cron issue. Following the 9/18 update, the recurring fee triggered fine, it created a new order, the order was received by Authorize.net.
The only issue I have now is some oddity with the saved credit card number (see http://drupal.org/node/582340)
Not a big deal, so I am very happy with this module now. Thank you again!

univate’s picture

univate commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.