Plan change prorate on a canceled subscription is not allowed. Reactivate first.
We are seeing a new error in our logs: "Plan change prorate on a
canceled subscription is not allowed. Reactivate first."
We believe this is triggered somehow by users trying to make a
payment to activate their cancelled subscriptions.
Here are a few examples from the CG errog log:
04/18/2011 14:53:43 765922 401 Plan change prorate on a canceled subscription is not allowed. Reactivate first.
04/13/2011 15:36:20 742304 401 Plan change prorate on a canceled subscription is not allowed. Reactivate first.
Can you please explain what this means, what causes it, and what we can do about it?
Thank you.
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Marc Guyer on 18 Apr, 2011 10:45 PM
Hi Dan -- It looks like you might have found a bug there.
We had a bug a while back (which you guys brought to our attention) which caused some issues when a prorated plan change occurred on a canceled subscription. That's effectively two actions in one request: 1) a subscription reactivation, and 2) a prorated plan change. Each of the actions require a credit card transaction. The reactivation transaction could succeed and the plan change transaction could fail. Icky.
We solved it by honoring the reactivation portion of the action even if the plan change transaction was declined.
Our current theory is that since both of the log entries you reference show a plan change from a free plan to a paid plan (instead of paid to paid), the improvement we developed isn't catching it.
We'll test that suspicion soon. In the meantime, there is a workaround if you want to hear it.
Support Staff 2 Posted by Marc Guyer on 19 Apr, 2011 10:29 PM
Yup. That was it. We've just deployed a patch. You shouldn't see that error anymore.
Marc Guyer closed this discussion on 19 Apr, 2011 10:29 PM.