#ab_api

1 messages · Page 1 of 1 (latest)

viral stagBOT
#

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

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

old jolt
#

Could you share the params information and the error stacktrace that you received?

#

I could see the successful in the first 3 requests, and only the last one failed: req_v29zjUnxazFG1BUFu

#

Looking into it now

old jolt
#

Looks like this error didn't always occur. I'm checking with the relevant team on why this happened

old jolt
#

Our team is investigating on why this happened and it might take a while. I'll be sending a message to you for the link to write in to us, so that we can follow up with you on this matter.

viral stagBOT
#

Hello @agile cove, we have sent you a direct message, please check it at https://discord.com/channels/@me/1418660710962958619

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
old jolt
#

Please let me know once you write in to us, so that I can escalate the case to the right team and keep you updated on the status

viral stagBOT
agile cove
#

Hi - Thank you for the quick response. I followed the link and have sent an email with all the details. Attached is a screenshot.

#

Also to your earlier question, yes for some reason the requests arbitrarily fail. I am using the auto iter and somehow it was able to iterate for the first 3 requests but then the 4th one failed to pass the page parameter. Since the cursor definition changed, we are probably getting the error message of invalid fields

#

If you notice on the 4 requests that were sent, the first one had the right start and end date that I had provided. For the 2nd and 3rd request, the iterator automatically populated the page param and made successful calls. However for the 4th call, somehow the iter wasn't able to populate the page parameter and the 4th request now seems exactly similar to the 1st request. There is no client side code issues as I am just doing the for loop over the iterator and the subsequent get calls are all from the SDK