Pro-Sites Not handling blog id's with customers that have expired stripe subscriptions

I believe pro-sites-files/gateways/gateway-stripe.php at line 3362 is shooting off an error when the blog is hit with a customer that has an expired subscription:

public static function get_blog_subscription_expiry( $blog_id ) {
                //Return If we don't have any blog id
                if ( empty( $blog_id ) ) {
                        return '';
                }

                //retrieve Customer Subscription
                $customer_data = self::get_customer_data( $blog_id );

                $customer_id = ! empty( $customer_data ) && ! empty( $customer_data->customer_id ) ? $customer_data->customer_id : '';
                $sub_id      = ! empty( $customer_data ) && ! empty( $customer_data->subscription_id ) ? $customer_data->subscription_id : '';

                //Return If we don't have customer id
                if ( empty( $customer_id ) || empty( $sub_id ) ) {
                        return '';
                }

                $expiry = '';

                try {
                        //Get the Subscription details
                        $customer = Stripe_Customer::retrieve( $customer_id );
                        //If there are any active subscriptions
                        if ( ! empty( $customer->subscriptions ) ) {
                                $subscription = $customer->subscriptions->retrieve( $sub_id );
                                $expiry       = ! empty( $subscription->current_period_end ) ? $subscription->current_period_end : '';
                        }
                } catch ( Exception $e ) {
                        error_log( "Error in " . __FILE__ . " at line " . __LINE__ . $e->getMessage() );
                }

                return $expiry;

        }

The error it send out is:

Customer cus_XXXXX does not have a subscription with ID sub_XXXXX

True...but this isn't error this an expired subscription. So all the sites that have expired subscription from all the years will be filling up the logs with these errors...why.

Please review the try statement, and lets make an adjustment that doesn't fill up logs. I dont think this isn't a server or code error, this is a logic error.

Thanks