• Resolved SwizzleStick

    (@swizzlestick)


    Yes, as the title says it does seem to be caused by having this plugin activated after the most recent updates. It was literally the only change made (WPForms plugin updated successfully from the plugins page) and within that 3 hour timespan every scheduled recurring order [schedule to renew in that timespan] failed to process properly.

    We’re not going to be using WPforms anymore for this particular website [so we don’t need a resolution for this], but I wanted to give your developers a headers up. I also notice in the action scheduler failed logs a few days prior: “action failed via Async Request: Scheduled action for wpforms_admin_builder_templates_cache_update will not be executed as no callbacks are registered.”, but it appears that subscriptions were renewing properly (or their scheduled actions weren’t failing) until the update to 1.9.1.x. No other failed scheduled actions in the log for a few years prior to those entries. We were on 1.9.0.4 before updating to 1.9.1.1/1.9.1.

    Everything is/was up-to-date with WP, WC and WC Subscriptions.

    2024-09-26T13:50:05+00:00 ERROR scheduled action 902200 (subscription payment) failed to finish processing due to the following exception: Error: Unable to create renewal order with note "Subscription renewal payment due:". Message: Trying to access array offset on value of type null in /home/example/public_html/wp-content/plugins/woocommerce-subscriptions/vendor/woocommerce/subscriptions-core/includes/class-wc-subscriptions-manager.php:151 CONTEXT: {"action_args":"subscription_id: 123456","error_trace":"#0 \/home\/example\/public_html\/wp-content\/plugins\/woocommerce-subscriptions\/vendor\/woocommerce\/subscriptions-core\/includes\/class-wc-subscriptions-manager.php(116): WC_Subscriptions_Manager::process_renewal(123456, 'active', 'Subscription re…')\n#1 \/home\/example\/public_html\/wp-includes\/class-wp-hook.php(324): WC_Subscriptions_Manager::prepare_renewal(123456)\n#2 \/home\/example\/public_html\/wp-includes\/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)\n#3 \/home\/example\/public_html\/wp-includes\/plugin.php(565): WP_Hook->do_action(Array)\n#4 \/home\/example\/public_html\/wp-content\/plugins\/wpforms-lite\/vendor\/woocommerce\/action-scheduler\/classes\/actions\/ActionScheduler_Action.php(56): do_action_ref_array('woocommerce_sch…', Array)\n#5 \/home\/example\/public_html\/wp-content\/plugins\/wpforms-lite\/vendor\/woocommerce\/action-scheduler\/classes\/abstracts\/ActionScheduler_Abstract_QueueRunner.php(88): ActionScheduler_Action->execute()\n#6 \/home\/example\/public_html\/wp-content\/plugins\/wpforms-lite\/vendor\/woocommerce\/action-scheduler\/classes\/ActionScheduler_QueueRunner.php(169): ActionScheduler_Abstract_QueueRunner->process_action(602291, 'WP Cron')\n#7 \/home\/example\/public_html\/wp-content\/plugins\/wpforms-lite\/vendor\/woocommerce\/action-scheduler\/classes\/ActionScheduler_QueueRunner.php(139): ActionScheduler_QueueRunner->do_batch(25, 'WP Cron')\n#8 \/home\/example\/public_html\/wp-includes\/class-wp-hook.php(324): ActionScheduler_QueueRunner->run('WP Cron')\n#9 \/home\/example\/public_html\/wp-includes\/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)\n#10 \/home\/example\/public_html\/wp-includes\/plugin.php(565): WP_Hook->do_action(Array)\n#11 \/home\/example\/public_html\/wp-cron.php(191): do_action_ref_array('action_schedule…', Array)\n#12 {main}"}

    That was a big yikes. We were using WPforms for a single feedback form, so it was easier to swapping for another form plugin and things went back to normal. I can always provide more details, but won’t be attempting to use this plugin again on this website because of thousands of subscriptions.

Viewing 1 replies (of 1 total)
  • Plugin Support Kenneth Macharia

    (@kmacharia)

    Hey @swizzlestick

    Thank you so much for bringing this to our attention and providing the detailed information and stack trace. I completely understand your concern, especially when managing a large number of subscriptions – that kind of disruption is definitely stressful.

    We were made aware of this issue earlier on and our team quickly investigated and released a fix in version 1.9.1.2, so this shouldn’t happen moving forward. While I understand you’ve decided to move away from using WPForms on this particular site, I really appreciate you taking the time to share your experience with us. If you decide to revisit the plugin in the future or need assistance with anything else, please don’t hesitate to reach out.

    Thanks again, and I’m glad to hear things are back to normal for you!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.