#aboom_api

1 messages ยท Page 1 of 1 (latest)

sharp sunBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1358665062080057466

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

naive escarp
#

Can you shar with me the subscription ID?

gaunt crown
#

yes one sec

#

sub_1RB6E703by6K3yx4kGrjJNpN

sharp sunBOT
granite geyser
#

Thank you, looking

gaunt crown
#

Yup, pls lmk if u need anything else!

granite geyser
#

Hmm okie, do you see the same thing on Test mode?

gaunt crown
#

Yes, same behavior

granite geyser
#

Can you use Test clock in Test mode, then advance the time to see if it is reflected?

gaunt crown
#

will do

#

Yea I created a billing event, fast forwarded to a month so the theoretically the user would have been billed for it in the invoice but it didn't show up

granite geyser
#

Which means the meter event never got counted? Weird. Could you share the test Subscription, and the request id (req_xxx) where you register Meter?

gaunt crown
#

sub_1RB7xO03by6K3yx4douWs6n7

#

req_WsYCzJXCFtBFZ9

granite geyser
#

I see the meter usage here

gaunt crown
#

Yea I tried again for the second month and it worked

granite geyser
#

Maybe you want to advance the Test clock a bit after registering usage, so the meter got recorded, then advance again

gaunt crown
#

it still didn't register my 1 usage for the first month though

granite geyser
#

Posisbly because when you registered 1 usage on first month, you didn't give it a bit of time to be recorded

#

so after you report the usage, advance the clock a bit, ie. says 1 hour

gaunt crown
#

In live mode these usages aren't being recorded though

#

and its been like an hour since these meter events

granite geyser
#

Um that's strange. The setup looks correct

#

Looking into them again...

gaunt crown
#

Currently this is what I see in my dashboard, maybe there is something wrong with it saying May 6 - May 6, 2025?

granite geyser
#

Um I think that's the reflection issue only. The next Invoice should be able to include those usage.

#

If you use Upcoming Invoice API, do you see the usage in API response?

gaunt crown
#

Can you walk me through how to use that

granite geyser
gaunt crown
#

Yea it looks like its not reflected in the upcoming invoice

granite geyser
#

Um I don't see usage on the Live mode meter event mtr_61SKU5MnGRqgeCuli4103by6K3yx4EYK ๐Ÿค”

gaunt crown
#

Please check the on_demand_judgees

#

i haven't done any events for the on_demand_traces

granite geyser
#

Ah mtr_61SKU5LS3hmrmgMxQ4103by6K3yx4NCa, okie seeing 3 but no records

gaunt crown
#

yes that is just because i ran 3 a few hours ago

#

the periods are in hour increments

granite geyser
#

Thanks. Do you have the request ids req_xxx for when you reported?

gaunt crown
#

sorry how can I get the request ids?

granite geyser
gaunt crown
#

req_v2dn1phsZuQ6BPN7Z

#

req_v2wI4TQ5L6jbjA053

#

req_v2NEkJgEikxPAqvyd

granite geyser
#

Ty. Running out of idea TBH.. Let me ask my team too

gaunt crown
#

Nw, thanks!

granite geyser
#

Hi there, this looks really strange and could you write in Support and mention you have discussed with Stripe developers on this Discord thread?

#

Please provide them this thread URL. We will then pickup from there and investigate further

gaunt crown
#

Okay! Where exactly should I send?