#jshirley_price-tiers
terse siloBOT
👋 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/1278770793266020414
📝 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.
- jshirley_api, 3 days ago, 16 messages
deep iris
Do you have an example where it worked before so I can compare the 2 requests?
hard pulsar
this is the working one
and this is the failed one https://dashboard.stripe.com/test/logs/req_gl1VRMTc5VzAcp
deep iris
Can you try the first one again? The one failing is different right now and has a "floating point" in the up_to
I can reproduce if I pass up_to: '10.0' but it works with up_to: '10' for example. I'm trying to figure out if we just changed this or if your code changed and started passing a floating point instead of an integer
deep iris
still that error is super confusing so I'll get it fixed. But I have a feeling that's the issue here and not that we changed our validation