#Pierre Lorin Elyn
spring relic
primal narwhal
Hello 👋
Do you have an example of these requests? I don't think its an issue from our end however looking at the timestamp should confirm if these were indeed sent twice or not
sturdy mesa
yes, i can give you all the data you want, can I send them in private message for security purposes?
primal narwhal
You can share the request IDs here
https://support.stripe.com/questions/finding-the-id-for-an-api-request
Those are safe to share 🙂
sturdy mesa
req_KPXYkzyKuYYYsq
req_jYN5UlO8ffVcPH
these are the two requests. From the stripe interface I can see the body is the same, but the keys aren't in the same order
amount and currency are interveted
primal narwhal
Yeah okay so if you look at the timestamp and Idempotency key, they're both different for two requests
https://dashboard.stripe.com/logs/req_KPXYkzyKuYYYsq -> made on 2022-10-08 01:35:13 UTC
https://dashboard.stripe.com/logs/req_jYN5UlO8ffVcPH -> made on 2022-10-08 01:35:16 UTC
Both came from same IP and were made by stripe-python library
sturdy mesa
Agreed on that, but given our logs and our code, it's very unlikely we sent them twice
hence the question 🙂
Have you ever had this kind of issue? It could be the cause of load balancing, that sent the request on 2 devices?
the fact that the json body of the post request isn't displayed with the same order is a bit strange
primal narwhal
Yeah that's def weird, I personally haven't come across any situation like this.
Do you have automatic retries configured by any chance?
I doubt that could be an issue but just wondering
https://github.com/stripe/stripe-python#configuring-automatic-retries
sturdy mesa
we haven't set any of this
but as i see the idempotency key is created locally right?
from the python library
hence it's definitely from our side 😅
primal narwhal
Yup 🙂 I'd recommend adding some logging and checking outbound requests to see what's causing this behavior
primal narwhal
NP! 😄 Good luck