#ashtray-wasp_api

1 messages · Page 1 of 1 (latest)

sage heraldBOT
#

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

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

uncut mantle
#

Can you share the other req_xxx where the results differ and share the associating JSON too (we unfortunately don't log the responses of GET requests)?

thorn blaze
#

This is the ID of the request:
req_lqrqf1ZCpwPUZa

muted crater
#

Hi there 👋 jumping in as my teammate needs to step away. I'm pulling that up.

#

There are quite a few invoices in that output. Can you point me to which one doesn't seem to have the expected value?

thorn blaze
#

Each of them except the first one

muted crater
#

I see, thank you! Taking a closer look.

#

I'm trying to see if I can reproduce this behavior in my test account, and so far I'm not able to. You mentioned seeing this behavior sometimes, have you noticed any sort of a pattern there? Is it based on where the request is made from, or perhaps the structure of the query you use?

thorn blaze
#

I've only tried this doing invoice search with this query, limit being 8, expanding data.customer and page parameter being specified (doesn't have to be a specific parameter). It returns an invalid result in roughly 25% cases. My teammates have observed this too. We've been seeing it only in test mode so far

muted crater
#

Gotcha, I'll see if I can reproduce when leveraging expand like that. Apologies for the delayed responses, the server is quite busy at the moment.

muted crater
#

I think I'm seeing it now sometimes when expanding data.customer. I'm going to look in this a bit more and then work on getting it reported to the right team for futher investigation.

thorn blaze
#

Thanks!

#

Will there any ticket ID that I could subscribe to?

muted crater