ARB expired, how to proceed in CBsubs?

Got an email that an ARB in authorize.net expired after only 1 recurring. I checked the subscription area and the "Recurrings Used" = 1, and the "Maximum recurrings" = "unlimited".

Why would an ARB ever expire if it is set to "unlimited"?

This is the notification from authorize.net:

Your Automated Recurring Billing (ARB) subscription 23450723 has
expired.

SECURITY STATEMENT
It is not recommended that you ship product(s) or otherwise grant
services relying solely upon this e-mail receipt.

RECURRING TRANSACTION INFORMATION
Subscription ID: 23450723
Status : Expired
Transaction : 1 of 1
Invoice : 54ybw4by5ybwb
Amount : 100.00 (USD)
Payment Method : Credit Card

Does the user get notified? How should we proceed with this?

Thanks guys

ok, some further investigating shows that the credit card for this user was declined and the ARB was canceled.

However, in CBcubs the user is still set to "Autorenew type = Mandatory" and "Autorecurring type = auto recurring with notifications"

Why did CBcubs not convert this subscription to "Manual" when her ARB was canceled? - and also sent her an email with this notification that her payment was declined and for her to update her card on our website?

The reason I'm asking is because all of our users are on an ARB and now, 1 year later, a lot of them are coming back as declined but it seems CBsubs is not converting these users to a manual renew type and therefore they are not being notified properly.

Here's my real issue: my client is very upset at me.

Am I missing some sort of option in the Config possibly that would fix all of this? I know this is all very complex, but maybe I set something up incorrectly?

**edit** Silent Post URL is set up properly on authorize.net and also correctly set to "set at authorize.net" in CBsubs gateway options

1) Did you get a notification (silent post url) about that ARB cancellation in CBSubs Notifications ?

2) If not, do you see any log or error about such a cancellation in CBSubs History logs ?

1) last thing in "History Logs" for this Subscription was the payment last year. I checked Baskets, Payments, and Subscriptions and no sign of any error or other entry of any type for 2016.
2) If you mean History Logs, no - nothing froths year. The only thing we got was the notification email from authorize.net; otherwise, we would have no idea that this payment failed.

ThePiston wrote: 1) last thing in "History Logs" for this Subscription was the payment last year. I checked Baskets, Payments, and Subscriptions and no sign of any error or other entry of any type for 2016.
2) If you mean History Logs, no - nothing froths year. The only thing we got was the notification email from authorize.net; otherwise, we would have no idea that this payment failed.

Without Silent POST coming through, CBSubs cannot guess that the ARB failed and that the automation failed.

3) Did any other Silent POST come through and is visible in CBSubs notifications ?

If not, and they are configured properly at Authorize.net, you should check if you see any Silent POST in your Apache server access logs (and Apache Error logs). If you don't see anything, then you should check with Authorize.net what's the status on their Silent POST successes, and if ok, also with your hoster why they don't come through. E.g. if a mod_security rule or a firewall or other system of the hoster doesn't let them come through.

Would I search for the silent post URL or some other keyword to find the error in logs?

I pasted the silent post URL directly into my browser and saw this:

ARB-Silent: ARB silent post Hash check failed