#geoffdgeorge_api
pastel graniteBOT
👋 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/1283853269696909473
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
brisk grove
Hello! The Search API sometimes requires a bit of time to provide results after setting or updating what you're searching for. How long ago did you set the metadata you're searching for?
noble hearth
Hello! There are some customers I'm seeing this for that were created more than an hour ago. The ID in the curl above is for a customer that was created at 11:52 am, so almost an hour and forty minutes at this point.
Historically we haven't seen it take this long to show up in search.
brisk grove
Ah, yeah, it shouldn't take that long. Can you provide the request ID of your search request as well as the Customer ID with the metadata you're searching for?
noble hearth
Customer ID is cus_Qpw8tExNz8yfU6. Request ID I think is req_A7uZaNjdkwoMqg.
brisk grove
Ah, so this Customer is using a Test Clock, and I don't think Customers with Test Clocks can be found with the Search API, but let me confirm that...
noble hearth
Hmm, I have other test-clock users I've been able to find through the search API.
We also have non-test-clock users that we've created in the past couple of hours that we're also not finding in search.
brisk grove
Ah, you're right, I'm thinking of the List API, which requires you to specify a Test Clock to list things associated with it.
noble hearth
Let me know if you need any of the other customer IDs and request IDs. Like I said, we're also seeing it for non-test-clock users created in the past hour and a half or so.
brisk grove
Taking a look now, give us a few minutes to investigate...
pastel graniteBOT
brisk grove
Ah, okay, so we have a delay in our internal search pipeline. We're working on it now, and it should hopefully be back to normal soon, but we don't have an ETA yet for recovery.
noble hearth
Any idea how widespread the issue is? Is this likely to affect our live environment as well as our test environment?
tawdry wren
Hi there 👋 jumping in as my teammate needed to step away. Based on what I'm seeing I do believe this is impacting both live and testmode, but will let you know if I find out otherwise.
tawdry wren
Our teams are working to resovle this, but there isn't much more I can share here in the meantime so I'm planning on closing this thread. Please let me know if there are concerns with that.
noble hearth
OK, no more updates on ETA?
tawdry wren
No, I don't have any updates. I can see our teams are acitvely working on it, but most of my focus is going to answering the other threads here on the server. I don't have an ETA to share either.
noble hearth
OK, thanks.