#Vitalij
lilac ferry
You should be able to update the subscription immediately after, however you need to be aware that for complex objects like that you may encounter object lock errors:
https://stripe.com/docs/rate-limits#object-lock-timeouts
If you expect to make a change immediately after creation, consider if you can include that change in the initial create request
wary meadow
Gotcha, I guess you are using some sort of distributed lock to avoid race conditions. Unfortunately, it looks like that we can't do it in one request. And would be true for search requests as well? So if I search subscriptions for a particular one with specific metadata, would that be also strongly consistent or do you need time to build those indexes?
lilac ferry
No, the search API is explicitly not meant for read-after-write
Don’t use search for read-after-write flows (for example, searching immediately after a charge is made) because the data won’t be immediately available to search. Under normal operating conditions, data is searchable in under 1 minute. Propagation of new or updated data could be more delayed during an outage.
cursive citrusBOT