#mancharface_balance-history-500
hollow groveBOT
👋 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/1481063388116287598
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
silent siren
Hello 👋
A 500 usually means something on our end is wrong. Give me a minute to check out what's going on with this request
silent siren
Okay this looks like it was a memory issue due to the amount of records being returned. Still digging
peak crown
Thanks for looking. Happy to change things on my end if I need to tweak things.
It is a whole lot of records.
silent siren
Yeah I think if you could try it with fewer records. I'm seeing internal logs that suggest the sorting buffer might have been maxed out.
As a test, try dropping the limit param down to 50
peak crown
Okay, I'll make an update and try again later. So this would be a limit of 50 but still using pagination. Am I understanding correctly?
silent siren
Actually, on reflection, I would try setting the limit to 10 and yes you can still use pagination.
peak crown
Okay, that then means 10x more calls to stripe. Fine with me if that's what you recommend.
silent siren
I realize that but the current approach is failing. You can test with 10 and increment up if that succeeds.
peak crown
No problem. I appreciate the help!
silent siren
I have also flagged the 500 error internally so we can follow up on that.
hollow groveBOT
mancharface_balance-history-500