ben-syndica_api

[bold talon]

👋 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/1340006725322936361

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[worldly flame]

I need help, someone stolen my identity

[twilit flax]

@worldly flame This is someone else's channel. Please reach out to support for help with that, we can't help with that here.

[worldly flame]

Please may I dm you? I am panicking

[twilit flax]

I can't help - you'll have to reach out to support.

[worldly flame]

Where i can reach the support?

[bold talon]

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

• 🧑‍💻 You must be a developer
• 🛠️ Your question must be about building a Stripe integration
• ⚙️ Your question must be technical/developer focused
• ⏱️ You must be available to respond in realtime
• 👥 You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.

[twilit flax]

@ben-syndica Sorry about that. Let me dig into this.

[worldly flame]

Thanks for the help, I am sorry for causing troubles

[twilit flax]

Believe it or not I didn't forget; my internal load balancing algorithms are not great. 😅 Still digging.

[twilit flax]

So so sorry. 😢 Any chance you have the Request ID for that request?

[peak torrent]

No, not recorded.

[twilit flax]

Fair. It's not a terrible thing to log, for what it's worth.

Ok I am ~fully focused on this now. Thank you ♾️ for your patience. ❤️

[twilit flax]

https://docs.stripe.com/api/usage_records/create#usage_record_create-timestamp

The timestamp of that usage record is exactly the same as the timestamp of the period end; was that the last item added to that billing period?

https://dashboard.stripe.com/logs/req_TT2n2VWJYYSb4K is the Request. It looks like it occurred very shortly after the Feb 1 invoice was created - like 0.86something seconds after. It also looks like the invoice was triggered by this request from y'all: https://dashboard.stripe.com/logs/req_TT2n2VWJYYSb4K

[peak torrent]

1. Is the issue the timestamp?

If yes, we can update code.

And does that mean that specific usage_record will be in the next invoice?

[twilit flax]

It should be, yes.

[peak torrent]

Got it, makes sense now.

[twilit flax]

Perfect. Again, sorry for taking so long - I'm just getting back into the flow of this "coversations everywhere all the time" model of working.

Is there anything else I can do/asnwer?

[peak torrent]

No, thats it. Thanks for looking into it. Bye