#pablo_error
brave skyBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1251173895977828434
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
mystic cosmos
https://pypi.org/project/stripe/
this is my custom class that interacts with stripe:
woven oxide
Which part is timing out
mystic cosmos
The detach seems to have timed out, same for setupintent
do i have a way to intercept those timeouts so i can react properly?
It would be ideal if you guys could check the logs in your side to see if you detect any anomalies
woven oxide
Sure
If it's timing out, generally that means we wouldn't have a log
What's your account id though?
mystic cosmos
account id: acct_1HCQMyIudlrw5tcZ
Im obviously working with test_mode right now
woven oxide
Yeah not seeing any anomalies
Did anything else change in your infra other that the sdk version?
mystic cosmos
so we are monitoring our service and it seems after updating the stripe version its CPU and Memory utilization went through the roof
have you guys receive any reports of this?
fleet wolf
Hi there 👋 when you see a timeout on your end (I'm guessing you're seeing those in your application somewhere?), are you still seeing corresponding requests being generated in Stripe and logged in your request logs? If so, can you share the ID of one of those, it should have a req_ prefix.
Have you set up automatic retries in your integration to help smooth over intermittent network issues?
https://github.com/stripe/stripe-python?tab=readme-ov-file#configuring-automatic-retries
mystic cosmos
We ended up updating our aws service ram and now it works, there might be something going on there, sry for your time guys