#eloi_webhook-event-delivery-retries-retention

1 messages ¡ Page 1 of 1 (latest)

signal havenBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1430957198225313956

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

spice nymph
#

Hi there,
where exactly do you see this notification in the dashboard? Can you give me a screenshot?

karmic ingot
#

There is a payment intent created around Oct 2, 2025 10:21 AM that is only received by our system at Oct 2, 2025 11:20 AM

spice nymph
#

Ok got it. First of I want to mention that we in this channel are not experts on Dashboard issues. In those cases we normally have to refer to the Stripe support. https://support.stripe.com/?contact=true
With that being said, the notification of 15 days for webhook attempts to conected platforms is a limitation of the dashboard and (at least as far as I know) there is no workaround.

karmic ingot
#

Do you know if there is a way to get those logs by the api? or I should go to support instead?

spice nymph
#

You should be able to retrieve the event using the Events API and check the object data, though this probably won't show delivery attempts specifically. If you need more information about a failed webhook event attempt you would need to reach out to support. When I look at the event you shared, I can see that this event was not send to any webhook endpoint.

karmic ingot
#

Oh, I mean the evt_3SDnNYJndt3DEfYu0GyhMZch, the charge.succeeded event

#

can you see if it did?

spice nymph
#

Let me check. It's a bit more work since it is outside the 15 days retention time to investigate. But let me take a quick look.

#

Alright, I can see that this event was sent twice to webhook endpoint we_1LHsiqIqT4glj2lD9WjYONpx

karmic ingot
#

and the first event failed?

spice nymph
#

At 2025-10-02 14:21:32 it timed_out

#

At 2025-10-02 15:22:25 it succeeded

karmic ingot
#

Oh, I see, perhaps our server was down or something. Do you know why it takes on hour between attempts?

spice nymph
#

If a webhhok attempt fails we normally retry over the course of three days with an exponential back off. We initially wait an hour probably to make sure that temporary server outages may be resolved etc.

karmic ingot
#

Curious if it's possible to reduce the gap to like 20 minutes or something, is that possible?

#

By the way, thank you so much, that makes sense what you said

spice nymph
#

I can forward your question about the wait time for reattempting as a feature request to the product team if you like.

karmic ingot
#

Yes, thank you so much

spice nymph
#

Got it. Will do in just a moment. I am filing a feature request for another user at the moment.

#

Alright I took the liberty and added you to the existing feature request about giving the merchant control about retry attempts schedule/time/etc.

karmic ingot
#

Thank you so much, have a good evening

spice nymph
#

Thank you. You too.

signal havenBOT
#

eloi_webhook-event-delivery-retries-retention