#torn_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1446305603952840768
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! I just want to acknowledge the question. I'm working on some other threads but will get to you as soon as I can!
thanks for waiting, could I know if you have followed this guide when setting up Amazon EventBridge to recieve Stripe events: https://docs.stripe.com/event-destinations/eventbridge?
yes I did
so for context in this past week for invoice.created on this event destionation there was 57050 successful deliveries and the 1 failure
the one failure happened at same time the response time shot up. suggests maybe a quick outage on the aws side?
it could be, have you checked with AWS? On our end I'm seeing the error http_not_found, which suggest requested resource or URL path doesn't exist
I got this from evt_1SaRs5FNNCh4hFC62EdYJ6I0 for this webhook endpoint: we_1SaP23ENXZcsesgNHUiHIyhC
oh different webhook endpoint. that one definitely 404s someone on my team set that up in error.
the event destination endpoint im talking about is: ed_61TXpU4PyKRaOHd3M16PsalQMRSQkffliW9AhfR2GIoq
Oh I am unable to view ed_61TXpU4PyKRaOHd3M16PsalQMRSQkffliW9AhfR2GIoq. Could you share the webhook endpoint ID? It should be prefixed with we_123
Sorry, please ignore the previous message, i just got the view of ed_61TXpU4PyKRaOHd3M16PsalQMRSQkffliW9AhfR2GIoq
All I'm seeing is AMAZON_EVENTBRIDGE_DELIVERY_UNKNOWN_ERROR at 2025-12-04 02:02:18 UTC but the next retry ~30 seconds later succeeded at 2025-12-04 02:02:46 UTC. You may want to consider contacting AWS to check if there was a temporary downtime
ok will do thanks. appreciate you taking a look here!