nukesforbreakfast_unexpected | Stripe Developers | Page 1

high canyonBOT Jul 10, 2025, 7:37 PM

#

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

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

#

next jay Jul 10, 2025, 7:38 PM

#

req_34fENgDt1gevX5

bronze hull Jul 10, 2025, 7:38 PM

#

Hi 👋

Thanks for sharing the ID. Let me take a look

#

Okay so the problem is that this is a 400 status code and not your expected 429?

next jay Jul 10, 2025, 7:40 PM

#

right, because 429 is normally returned for rate limit errors: https://docs.stripe.com/rate-limits#handling-limiting-gracefully

bronze hull Jul 10, 2025, 7:41 PM

#

Yeah... This isn't an error I've seen before. Let me ask my colleagues about this.

high canyonBOT Jul 10, 2025, 7:46 PM

#

bronze hull Jul 10, 2025, 7:53 PM

#

So it looks like this is a long-standing, known bug in our API. I'm flagging this friction internally so we can hopefully get it addressed.

#nukesforbreakfast_unexpected