#zach_meters-v2

1 messages · Page 1 of 1 (latest)

proud estuaryBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

sage spade
#

oh boy this is my life now 😂

#

zach_meters-v2

#

Can you clarify the exact error you get and whether you are making parallel requests? Can you also share the exact code?

left ridge
#

haha im sorry

#

i am making parallel requests

#

using AWS SQS queues, the code is the same as before, its now working in that it sends the call to stripe, but is getting rejected

#

getting u more info 1 sec

#

[ERROR] 2024-10-30T23:44:21.359Z 7921d9c4-79a8-5faf-b7ff-8658bebcda22 Error sending usage to stripe: Request req_v2dkyxZrT6yQFyGwG: Sorry, something went wrong. We've already been notified of the problem, but if you need any help, you can reach us at support.stripe.com/contact.

#

this is the exact error I get

sage spade
#

Okay so you aren't getting rate limits at all really?

left ridge
#

I am in some messages before it...

#

trying to get you that as well

#

but this is the one i see the most of, but seem to come right after the rate limit messages

#

digging it out for you rn

sage spade
#

Okay my guess is that you are hitting some rate limits in Test mode. Again this is all brand new and I wouldn't be surprised you're the first person to ever use this 😅

left ridge
#

Sure, im just trying to understand if thats the case, so i know if this will work in live mode.

#

But not clear how I can tell that

sage spade
#

Not sure either but looking

left ridge
#

[ERROR] 2024-10-30T23:43:15.942Z 29ec1158-8a99-5d86-a3d7-4ec44c4a89ce Error sending usage to stripe: Request req_v2b8VVpqFYFYYhxKh: Request rate limit exceeded. You can learn more about rate limits here https://stripe.com/docs/rate-limits.

Rate limits

Learn about API rate limits and how to work with them.

#

here is the rate limit error

sage spade
#

Okay unfortunately I don't think I can debug this here in real time I'm sorry. At this point I think you really should write to support directly and have a conversation over email with all your questions as you go. Unfortunately so much of this is knew and I don't have the right tools to investigate and debug those for you in real time on Discord I'm sorry

For now, please use https://support.stripe.com/contact to start an email conversation with the support team so they can guide you over the next few days/weeks for your v2 integration

left ridge
#

Ok sure. Let me try and do that. I do not mean to be bothersome at all. I am just trying to get the system working and have been having trouble as you know :).

sage spade
#

oh it's not on you at all here. It's just really bad luck because it's brand new and none of the usual tools we have work with those objects/APIs and I am unable to just find basic answers. It will get better over time but right now I think async questions over email will be best.