#steve_17024-usage-records
dreamy gale
cinder olive
quiet ferry
@worthy solstice Do you have an example request ID we can take a look at? (I'm also hopping in to take a look)
worthy solstice
it looks like setting timestamp to timestamp=1704552901 (1 more than the recommended value) works
but that's very misleading
here's an example where it fails:
https://dashboard.stripe.com/test/logs/req_7o1c2p5nX35J0L
quiet ferry
steve_17024-usage-records
worthy solstice
here's the suggestion from the response:
https://dashboard.stripe.com/test/logs/req_24HSE9f0jgUORy
here's what happens when i try suggested value:
https://dashboard.stripe.com/test/logs/req_2QGFAqy6xFJP0d
one less than suggested value:
https://dashboard.stripe.com/test/logs/req_TQKu7uXsruIl7L
one more than suggested value (seems to work, but is misleading):
https://dashboard.stripe.com/test/logs/req_SDTZH9vKKWviXp
quiet ferry
Gotcha - I can see why this would be confusing, and I think this is a case where the suggested timestamp from the error is just taking into account your test clock time, and not the current period of the subscription In your case, your test clock is currently set to the exact same time as the current start time of the subscription (which is currently 1704552900) so it's suggesting you set a time up until that point.
Really the best way to fix this is to advance your test clock to the timestamp you want to create the usage record for, and the create the request anew
worthy solstice
got it. thanks for the clarification
will make a mental note of it 🙂