#frallain
1 messages ยท Page 1 of 1 (latest)
Hi there!
Hey @tender kite ๐
Give me a few minutes to look into this.
So it looks like your tried to create the usage record between when the billing cycle ends, and the next invoice is actually generated. And when that happens we return this error.
So you should send your usage record either earlier or later to avoid this.
Interesting, this is clearly not stated in https://stripe.com/docs/api/usage_records/create
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
How comes usage record are that coupled to invoices?
Hey! Taking over for my colleague.
How comes usage record are that coupled to invoices?
Not sure I understand what you want to understand exactly? Did you retried the request ?
Yes, it eventually worked after retrying for 10min... but conceptually it should even work if there is still no invoice.
From a software engineering perspective :). Good luck with that and thanks for the information
Happy to help!
Hey, just to clarify, we have reported this behaviour to the responsible team and they will look into it. Obviously, this error should not be happening, given timestamp: "now".
Please, let me know if you have any other questions.