#Fugazcz
marsh mesa
gusty pebble
hi, do you have the two event IDs evt_xxx involved?
grim wing
yes, the IDs are different in each call
gusty pebble
sorry I meant, paste them here so I can investigate
grim wing
ok
The one which switched to "active" : "evt_1NiYAJKBfVxmDRxIAGrI9Xe3"
The second one which switch again to "trialing": "evt_1NiYAJKBfVxmDRxIUo4Y9R3b"
gusty pebble
strange, I guess it's a quirk when using the 'pause subscription' feature https://stripe.com/docs/billing/subscriptions/pause
probably we unpause the subscription internally first(which generates the first event), and then we update the status to trialing(second event), all of which is happening inside the same API call.
grim wing
What is the solution? Technically it looks correct because on the customizer the user has status active, but since we use this webhook to display data in the application, the user sees that he has status "trialing", although he has active
gusty pebble
I'd probably suggest writing to https://support.stripe.com/?contact=true to file a bug, since I agree this doesn't look right and we should try to make the update atomic. It's likely a quirk with this pause feature since it's not used much and we might have missed this exact interaction in testing.
grim wing
ok i will write it there. Is it possible to urge it somehow? It is very important to us
gusty pebble
the best first step is to get a support ticket so the issue can be escalated