#alexanderg-retries-Java
pale sparrow
Sure 👍
gusty dragon
Thank you for your patience, I believe either timeout threshold (connect for establishing a connection, and read for getting a response) will trigger a retry if exceeded.
pale sparrow
I see these defaults in Stripe.java
public static final int DEFAULT_CONNECT_TIMEOUT = 30 * 1000;
public static final int DEFAULT_READ_TIMEOUT = 80 * 1000;
is this 30 seconds and 80 seconds?
Is there a best practice for setting the timeout /retry combo?
(the number looks rather large by default)
gusty dragon
No, we don't have any sort of recommendations or best practices around this, if I recall correctly the automatic retries are disabled by default in most libraries.
pale sparrow
What is an automatic retry, is it the same as RequestOptions.setMaxNetworkRetries
Also, by default Stripe client would wait for 80sec to timeout?
gusty dragon
Some requests (particularly list requests) can take a while to build and transmit their response.
pale sparrow
I understand, we are doing a payment intent auth operation. Would it be expected to be quick. Also, could you please get back on the two questions in my above post.
gusty dragon
Quickish. Payment intent authentication involves our systems reaching out to the issuer of the payment method, so they take a little bit of time.
Yes those timeouts are set to 30 and 80 secs by default.
pale sparrow
Would there be a ballpark number for payment intent auth? e.g., 5-10 secs.
gusty dragon
No, we don't have any ballparks like that as there is a vast number of issuers and networks that we interact with.
pale sparrow
Sounds good. Thank you!