Mark a recurring subscription as canceled in Salesforce

[CnP.Support.AM]

Good day @wtben,

We try to login but we don't have access to the following OrgID: 00Dd0000000borB. Would you please make sure that we have access to your instance?

Looking forward to hearing back from you.

Thanks,

[wtben]

Sorry, my fault. I clicked the wrong popup menu. You're good now.

[CnP.Support.AM]

Good day @wtben,

Still we don't have access.

See Image:



Sorry but this time I would like to share the screenshot to make sure I am looking into the correct Organization.

Looking forward to hearing back from you.

Thanks,

[wtben]

I don't know why my access granting didn't save this morning. I've just set it again and it seems to be sticking this time.

[CnP.Support.AM]

Good day @wtben,

Thanks for granting access to us. We reviewed your instance and found that the recurring transaction which you are referring to has been cancelled and credited while you were having the old version of our apps in Salesforce. In the old versions we are not updating the recurring status.

We have re-pushed the data for last recurring transaction for above Recurring ID: 161720 and the status is updated to Cancelled.

Simply, you will need to re-push the transaction again from Connect for the last recurring transaction order number. This way it will update the status of recurring.

Regarding the account name, we can't update the account name for the recurring ID.

Please check and let us know if we can be of any further assistance.

Thanks,

[wtben]

Thanks for looking into this, AM. I'm still a little confused because reposting was the original instruction I received regarding this issue and it doesn't seem to have worked for me. You're saying that if I repost to Salesforce a transaction for a subscription that has lapsed, the subscription will automatically get marked canceled? Here are some other examples:

• Order 1611310435276481593563 for Recurring 158207 (this charge was declined)
• Order 151258104155416087064 for Recurring 157275 (this charge was declined)
• Order 1511297434815549161139 for Recurring 141705 (this subscription was canceled in Connect)

There are 12 more cases where the "recurring chain is out of sync." Take a look at the "Active Subscriptions incl. Lapsed view of C&P Recurring in our instance. Sort by Next Installment Date (ascending) and all 15 will be at the top.

What do you think?

- Ben

[CnP.Support]

Good day wtben

What you mean by cancelled and what we are referring to are different. The logic is a bit complex, and for a reason, so please see the following:

Here is how a recurring transaction works:

• When a recurring transactions is processed, the Next Installment Date is saved in the database.
• Every day the recurring engine runs transactions whose "Next Installment Date" matches the TODAY's date. In other words, when we run the recurring today all transactions whose "Next Installment Date" is for TODAY will run.
• If a transaction declines, the "Next Installment Date" will NOT update so it stays in the past.

A declined transaction will essentially be left behind and will never run again.

If you go to Connect or Salesforce you can retry the Declined transaction and charge all the missing transactions to bring a transaction up-to-date. Once the Next Installment Date is in the future, meaning greater than TODAY's date the recurring will be back in the queue.

In Salesforce, we have to have all the details of a recurring before we can perform any actions such as charge next, etc. If for any reason, any of the recurring transactions in the chain are not listed in the C&P Recurring as part of a recurring family, the family is out-of-sync.

Example:

• A recurring transaction has been going on for 20 months, on a monthly basis.
• After the 10th transaction the connection is lost and for 5 months the transactions do not post to Salesforce
• The connection is brought back online and two transactions post

as you see the above family is out of sync and Salesforce does not know what the last transaction is and if the transactions are going on, failed, declined, etc. etc. In order for Salesforce to perform any actions with the API it needs to know the exact information for the recurring. This is done to ensure data integrity and full knowledge of the action given the possibility of out-of-sync conditions which could create a problem, such as cancelling the wrong transaction or crediting the incorrect payment.

In summary, for Salesforce to perform any action it has to have full knowledge of all transactions.

Nothing in the system is "Cancelled' automatically. As stated by my original statement I meant we do not run it anymore- as it is out of the queue. If you wish to cancel it you need to cancel it in Connect so officially it shows as cancel. The reason we do not issue a CANCEL command is because you have the option to run it again and re-instate it by processing the declined transaction. You may also change the credit card number and resume the recurring.

Currently in 9.40xx release if the last transaction has declined and the recurring is out of sync as a result, the cancel button will not show up. In 9.50xx, due out the week of July 18, 2016 we are adding exceptions to allow for an out-of-sync recurring whose last transaction has declined to allow for cancellation. It currently considers it out of sync and will not allow any actions. If you want to cancel it manually you have to go Connect and do it.

I hope I have answered your question. I think I have explained a bit more than necessary but it is always good to know how a system works & thinks.

[wtben]

Ah ha! Not sure the whole explanation was necessary. The missing piece for me was that I needed to cancel the recurring in Connect in order for it to be canceled in SFDC. It seems no "repushing" or "reposting" is necessary.

[Perc-BRC]

FYI wtben They are adding a feature this next release to keep the Cancel button on the recurring transactions that are out of sync so you can mark them officially cancelled even after the transactions have stopped processing due to a lapse. I had the same issue and asked for a fix on the Power of Us Hub and it's getting added, I think this coming week. Yay!