Wp_blc_filters: Data: 0.02MB + Index: 0.00MB + Engine InnoDB Wp_as3cf_items: Data: 13.52MB + Index: 23.09MB + Engine InnoDB Wp_actionscheduler_logs: Data: 8.02MB + Index: 8.03MB + Engine InnoDB Wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Wp_actionscheduler_actions: Data: 10.03MB + Index: 17.13MB + Engine InnoDB W****o_products: Data: 13.52MB + Index: 2.84MB + Engine InnoDB Wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDBįakenames: Data: 2.52MB + Index: 0.00MB + Engine InnoDB Wp_woocommerce_payment_tokenmeta: Data: 1.52MB + Index: 0.69MB + Engine InnoDB Wp_woocommerce_payment_tokens: Data: 0.11MB + Index: 0.05MB + Engine InnoDB Wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB Wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB Wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB Wp_woocommerce_tax_rate_locations: Data: 0.11MB + Index: 0.14MB + Engine InnoDB Wp_woocommerce_tax_rates: Data: 0.08MB + Index: 0.06MB + Engine InnoDB Wp_woocommerce_order_itemmeta: Data: 448.98MB + Index: 387.97MB + Engine InnoDB Wp_woocommerce_order_items: Data: 25.55MB + Index: 8.52MB + Engine InnoDB Wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.05MB + Engine InnoDB Wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB Wp_woocommerce_sessions: Data: 14.03MB + Index: 1.02MB + Engine InnoDB Make /var/www/html/src/wp-content/uploads/wc-logs/ writable or define a custom WC_LOG_DIR.Įxternal object cache: ✔ Server Environment Log Directory Writable: ❌ To allow logging I can reproduce this bug consistently using the steps above.This bug happens with a default WordPress theme active, or Storefront.I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.Isolating the problem (mark completed items with an ): If applicable, add screenshots to help explain your problem. Try re-add the coupon, you'll be told "usage limit has been reached".
Checkout in a way that causes a failed payment.Create a coupon with a usage limit of 1.Steps to reproduce the bug (We need to be able to reproduce the bug in order to fix it.) I have searched for similar bugs in both open and closed issues and cannot find a duplicate.Ĭoupons with a usage limit are showing "usage limit has been reached" after a failed payment using that coupon.Ĭoupon should still be usable after a failed payment.Īpplying a coupon to an order (specifically with a usage limit of 1) and making a failed payment at checkout places a _maybe_used_by lock on the coupon itself - making it unusable by the same person.I have have carried out troubleshooting steps and I believe I have found a bug.Prerequisites (mark completed items with an ):