#yoni_api

1 messages ¡ Page 1 of 1 (latest)

split hareBOT
#

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

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

magic thicket
#

hi! probably best to open a support ticket at https://support.stripe.com/?contact=true with full details including exact raw JSON responses you're seeing. But this is a known issue for now unfortuantely, we've seen other reports.

obsidian granite
#

Is there a GitHub issue on this that we can follow?

magic thicket
#

no, it's tracked internally

obsidian granite
#

I see - would be great if this was documented somewhere, we spent quite a bit of time trying to figure out if we had a bug in our logic.

magic thicket
#

it's more just an internal bug/edge-case we're still tracking how many occurrences actually happen, than an expected limitation so it's not really going to be documented

obsidian granite
#

It reproduces quite consistently for us - happens 50% of the time.

heavy parcel
#

@magic thicket do you know what the scope of the issue is? Does this also happen for other search types?

#

And does this also happen for list APIs?

magic thicket
#

it's specific to the Search API

heavy parcel
#

So all Search APIs? Not just Subscriptions?

magic thicket
#

I think it might be all based on how the issue is described internally

#

anyway I think we have all we need here, the team working on this has been collecting examples and I shared your example with them. The team unfortunately doesn't have anything else to share, it's something on their roadmap to fix. The workaround for now would be to detect this and just skip the duplicates in your application code(like throw the IDs into a Set as you iterate and continue your loop if an value is already in it)

obsidian granite
#

Yeah - that's exactly what we're about to do. As far as you know, we only need this workaround for Search APIs (on any entity type)?