You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware that data is searchable with an expected delay of up to a minute and that you shouldn't use search for read-after-write flows as per the docs. However, I'm experiencing something that, IMO, should not behave this way even with this limitation in mind.
To simplify, after a charge is made, I'm searching for charges, filtering by customer and refunded:
const activeCharges = await stripe.charges.search({
query: `customer:'${customerId}' AND -refunded:'true'`,
});
However, I'm getting a list of charges, some of which have refunded: true. Even if the data is not updated at this point in time, I think charges that don't match the query at this point in time shouldn't be returned at all.
Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered:
What happened?
I am aware that data is searchable with an expected delay of up to a minute and that you shouldn't use search for read-after-write flows as per the docs. However, I'm experiencing something that, IMO, should not behave this way even with this limitation in mind.
To simplify, after a charge is made, I'm searching for charges, filtering by
customer
andrefunded
:However, I'm getting a list of charges, some of which have
refunded: true
. Even if the data is not updated at this point in time, I think charges that don't match the query at this point in time shouldn't be returned at all.Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered: