#adamclio
1 messages · Page 1 of 1 (latest)
HI 👋
Can you share a couple event IDs so I can take a look?
Sure - working in our dev environment and whenever I re-retrieve "evt_1NyGmbDAWTp2PXOwKBdcmQEa" or any other customer.subscription.updated events that the event.created I receive does not match the one in the event logs on Stripe.
I want to be clear that this happens when using Stripe::Event.retrieve
I'm seeing an event created of 2023-10-06 16:21:45 UTC, what are you seeing in your dashboard?
It's an integer: 1696609245 which converted to UTC is 2023-10-06 16:20:45 UTC
I'm looking at the actual HTTP POST request payload we sent for this account and I see "created": 1696609305,
But when I re-retrieve the event (in case of needing to re-process) I get: 1696609305 (integer) 2023-10-06 16:21:45 UTC
Yes but we are re-retrieving an event
the event.created (I would assume) should be matching when the event was initially created, not when the request is sent
If we look at the event payload, the created field is set to: 1696609245
But when re-retrieving it is set to: 1696609305
I only see the re-retrieved data in any relation to this event
I can't find the 245 timestamp anywhere on this object
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Not requests - events.
That is the created timestampe for the subscription
Event generation is inherently asynchronous and the Subscription creation and event generation are not expected to match
No worries! There's a lot of nested data in there and I sometimes need to double check