#eczo
cinder loom
amber pier
Hi! Let me help you with this.
Could you please share the Request ID req_xxx? https://support.stripe.com/questions/finding-the-id-for-an-api-request
tame edge
Sure
req_ZoTOjLNJ2nedbf
amber pier
Is it only one error of this kind?
Were you able to create usage records before?
tame edge
Yes before and after we can. The problem happens only when the period ends and the draft invoice still not created, during this period if we send create usage record, we receive an error.
We are using "usage record " API since six month, and there has been no change in code or our customer pattern recently.
We had multiple such errors.
Depending on our customer usage, our 2 % of customers are affected.
another requests ids: req_INRszEpWRHX2Ih, req_Osq8LewbijybID
amber pier
I see, thanks. This looks strange, indeed. Let me check.
amber pier
Hi, I think I've identified the issue, it seems like there's ambiguous time between the billing_cycle_anchor, and the time when the Subscription is actually updated and the new period starts. Then, we check if the timestamp is after the billing_cycle_anchor, and the request fails.
How often do you update the usage record?
Essentially, there should not be any issues in the logic, because if the usage happens after the billing_cycle_anchor (2023-05-09 17:15:49 +0000) it accounts for the next billing period, and you will have the whole month to update it correctly.
tame edge
About ~1600 usage records per day across all customers
tame edge
Essentially, there should not be any issues in the logic, because if the usage h...
exactly, that what we want)
amber pier
I will report your use case to the responsible team, but for now I recommend that you could retry the request after a few hours.
tame edge
Can you please create a ticket with this email: mike@callenq.com for we will stay informed about issue progress?
amber pier
I can't create tickets from my side. Feel free to reach our to Stripe Support: https://support.stripe.com/?contact=true
I also can't guarantee if or when this will be fixed, unfortunately.
You can mention my username in the ticket though.
tame edge
ok, thank you