#caturner81_unexpected
median falconBOT
👋 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/1356693450849783881
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fading scaffold
Hi there. Could you provide an example customer id from your own integration?
fresh crystal
Sure, this one got created over 15 minutes ago and still doesn't show up in metadata search
cus_S3FkI7jK8hQtYR
Just seems like your search indexing, which your docs say can take up to 60 seconds generally does work pretty quickly, it just seems to not be functioning right now as far as I can tell
fading scaffold
Interesting - seems to be working in test mode. Let me see what I can find out
fresh crystal
My test just now passed again for the first time in the last hour or so. So it may be fixed now.
Definitely seemed like there was an outage in that functionality for a while. These tests have been passing consistently for the past several months and were failing in our CI environment for the last hour or so.
that customer I posted has an organization_id set in metadata, I still don't get a result in the UI if I search for that UUID but older customers do show up by searching for their organization_id, but I'm not sure what endpoint the Stripe UI is using, so that might be different.
fading scaffold
still looking to see if there is something that might be linked to this
so if you do a query on Customers search like query: 'metadata['organization_id']:'50a9e8de-ca1b-5438-a541-3bf0c8668a30'' currently, you don't get 'cus_S3FkI7jK8hQtYR' in the results?
median falconBOT
fresh crystal
That was exactly what I had in my tests that was failing until a few minutes ago when it began workign again.
I'd have to do a little work to make that specific query via the API
the API does seem to be functioning again. What I'm saying I'm still seeing is searching by that UUID in your Stripe UI's search box isn't returning that customer, but that might be unrelated. I can search for older customers just by UUID in your UI's search box and they show up, but I'm not sure what mechanism that box is using.
That search box may have different guarantees than your API. The nature of this original issue was what appeared to be a total outage in indexing for about an hour where that specific metadata API search just stopped functioning for new customers.
serene gyro
Hello
Yeah, the dashboard is likely using some private APIs which aren't available publicly. My team won't be very familiar with that.
fresh crystal
Yeah, I think ultimately things are resolved, but it definitely felt like an outage of the indexing part of your system for an hour or so. I've had those tests in place for months and they wait a few minutes for indexing before they fail, and they were failing for about an hour earlier. Seems to have recovered now.
serene gyro
Yeah this is likely one-off (could also be due to today being 1st day of the month -- there might be a lot more data to ingest)
fresh crystal
Interesting. I'll keep an eye out for that in the future. We rely on that search endpoint (with the typical ~1 minute indexing time being acceptable), so if there are ever much longer delays in indexing we'll need to rethink some things.
Thanks y'all, seems like we can consider this closed.
serene gyro
NP! Sorry for the trouble 🙂
Have a good one