braydonf
commented
2 years ago This appears to be associated with running WordPress+WooCommerce+BTCPayPlugin with multiple replicas during the pairing process with BTCPayServer. Changing the number of replicas after pairing to not ameliorate the issue. Removing the token and repairing with only one replica seems to ameliorate the issue. So it looks like there may be an issue with the pairing process with BTCPayServer when there are replicas of WordPress.
Describe the bug
During an order there were duplicate events listed, these were all within the same minute. They are listed from from older to newer:
Stock levels reduced [redacted] 77→76
Order status changed from Pending payment to Processing.
Stock levels increased [redacted] 76→77
Order status changed from Processing to Pending payment.
BTCPay invoice payment completed. Payment credited to your merchant account.
Stock levels reduced [redacted] 77→76
Order status changed from Pending payment to Processing.
Stock levels increased [redacted] 76→77
Order status changed from Processing to Pending payment.
BTCPay invoice payment completed. Payment credited to your merchant account.
Stock levels reduced [redacted] 77→76
Order status changed from Pending payment to Processing.
Stock levels increased [redacted] 76→77
Order status changed from Processing to Pending payment.
BTCPay invoice payment completed. Payment credited to your merchant account.
As you can see there are three of each series of events. There was also three duplicate confirmation emails sent. And at about 40 minutes later, the order incorrectly changed status as being unpaid for a time limit:
Woocommerce System Status
Wordpress: 5.8.3 WC Version: 6.0.0 BTCPay for WooCommerce by BTCPay: 3.0.15
Your BTCPay Environment:
Additional context
This was running WordPress + WooCommerce with 3 replicas in Docker Swarm.