simin_80475

[cosmic ravine]

How did you measure the delay? Can you share example subscription and customer creation requests (req_xxx)?

[vivid pecan]

@cosmic ravine hi，I measure the delay by the log，as

@cosmic ravine hello, Is there s simple payment process?

[cosmic ravine]

Can you share the request ID (req_xxx) of these requests, so that I can check if there is any latency at Stripe end or whether the issue is with your network?

[vivid pecan]

req_id:d73e6a47e6de45af8f99ee1bfe3dc5ce
customer_id:8ba64f82dfe5474d9693d9331816bb9b

@cosmic ravine

[cosmic ravine]

This is not Stripe request ID. Stripe request ID is in the format of req_xxx

Customer ID is in the format of cus_xxx

I'd need either of them to check

[vivid pecan]

can you find the req by email?
[e-mail]

utc time:2023-09-18 11:40:32,893

[cosmic ravine]

No, I'm afraid I can't find the requests by email. I'd need a Stripe objects such as request ID (req_xxx), customer ID (cus_xxx), or subscription ID (sub_xxx)

[vivid pecan]

oh，I find the subscription ID:
sub_1NrfoeDIvHNr5wfCVXd3uCiE

[flat latch]

Hi @vivid pecan I'm taking over this thread

Is your primary concern the latency on customer creation API call?

[vivid pecan]

yes, sometimes customer.create cost 6s.

[vivid pecan]

as you can see the log

[flat latch]

Based on our internal log, it took only 0.183s to create the customer

[vivid pecan]

😂 , can you show me the call time and the response time?

[flat latch]

the start time is 9/18/23 11:40:33.019 AM UTC, we don't log the end time

[vivid pecan]

Is it because stripe sdk has a lock? We use python sdk, and because of some bugs, we may call customer.create twice in a short period of time.

[flat latch]

You can make your request idempotent to avoid duplicate https://stripe.com/docs/api/idempotent_requests?lang=curl#idempotent_requests