#Jkas
steel heron
delicate nebula
Hello 👋
The first event was generated for this request
https://dashboard.stripe.com/logs/req_JtOWJHaQTlRrvp
and the second event was generated forthis request
https://dashboard.stripe.com/logs/req_gmaCZffiXTCeso
these came from your own integration
sweet epoch
But for each one, they have duplicated webhook events. Same timestamp.
Same request ID, same idempotency_key
Look at the Webhook Events here: https://dashboard.stripe.com/events/evt_1MYcSuEkTO8kaKcKg90zUesl
delicate nebula
Not sure I completely follow.
Like I mentioned before, these events were generated by two different requests with two different idempotency keys
https://dashboard.stripe.com/logs/req_JtOWJHaQTlRrvp was at 2023-02-06 21:43:07 UTC that generated https://dashboard.stripe.com/events/evt_1MYcSuEkTO8kaKcKg90zUesl event
https://dashboard.stripe.com/logs/req_gmaCZffiXTCeso was at 2023-02-08 02:58:27 UTC that generated https://dashboard.stripe.com/events/evt_1MZ3rbEkTO8kaKcKVKa2QMZU event
These are not duplicate events in any sense.
sweet epoch
Ok, can we start over again?
Let's just look at one, I'm sorry we started with two.
https://dashboard.stripe.com/logs/req_gmaCZffiXTCeso came through
And generated the
https://dashboard.stripe.com/events/evt_1MZ3rbEkTO8kaKcKVKa2QMZU event
Please now go look at the event it generated.
There are 2 attempts, one success and one failed.
Can we agree on that?
sweet epoch
Right
That's what I'm talking about - why are these two attempts occurring at once?
Same timestamp, no delay.
They seemingly get fired off by Stripe at the same time for an unknown reason.
delicate nebula
there was a delay in between these two
The first delivery attempt failed at 2023-02-08 02:58:30 UTC
The second attempt was made at 2023-02-08 02:58:44 UTC which succeeded
the created timestamp is referencing when the event was generated and not when it was delivered
sweet epoch
How can I find these two different timestamps you're referring to?
Is that available in the UI?
delicate nebula
Not sure if they're available in the dashboard unfortunately.
I pulled them from our logs
sweet epoch
Are you able to send me all the timestamps with unique attempt ids?
I'm having trouble debugging this without all the information you have on your end.
attempt_id | sent_timestamp | response
I'm seeing the error on our end as a unique constraint issue, but the times you've given me don't add up. I'm not sure how the first one could fail and the second succeed unless they were sent simultaneously.
This is when our local record was created, perhaps a clue?
I wonder if there's another webhook getting fired off 2 seconds prior to this one.
No, this time adds up
I need to better understand these two attempts, so any additional context would be extremely helpful.
delicate nebula
The first attempt received a 500 internal server error as response
sweet epoch
Ok, so we returned an error but it looks like the records on our end was created successfully. So there's a bug on our end for returning the 500.
I appreciate your help!
delicate nebula
NP! 🙂 Sorry for the confusion earlier
delicate nebula
Have a good one! 🙂