#lec1892_api
hearty folioBOT
👋 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/1245018097052680284
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
spark relic
Hi 👋 that is expected behavior, it takes time for objects to be indexed to be searchable by our Search API. That's why we avoid using it in flows where you need realtime data.
Don’t use search in read-after-write flows where strict consistency is necessary.
https://docs.stripe.com/api/customers/search
If you're going to need to be able to search for these Customers shortly after their created, you will likely need to store those details on your end so you can index and search them. Is it possible for your flow to use the Customer ID that is returned to you when you create the Customer object?
kind thistle
Unfortunately, the customer ID can't be used in my flow.
So I should keep the retry mechanism. It keeps searching for the customer until it is returned.
spark relic
Gotcha, you may want to consider building your own database to track those associations then, if you need to query them sooner.