#ryankimm-draft-invoices
light aurora
yes
summer mural
Do you have any webhook endpoints listening to invoice.created events?
light aurora
not sure.
summer mural
Can you provide the ID of an invoice where you're seeing this?
summer mural
Invoice ID would be preferable, it should look like in_XXX where XXX is an alphanumeric string.
light aurora
in_1KkdDMIhet1rbHUx1bOkdBF5
summer mural
Thanks, pulling it up now
light aurora
Great- I had already went ahead and 'manually' charged a handful of customers today because their payment was due yesterday
summer mural
So you have three webhook endpoints listening to all events. One has been disabled, but there is one that is not responding to events we're sending. When you listen to invoice.created events, if we don't get a successful response from all of your endpoints for the event then we delay the finaliztion of the invoice until our webhook event retry logic is exhausted. This is typically about 72 hours.
I'd recommend tailoring your endpoints to only listen to events that you're actually taking action on.
light aurora
Hmmm. ok. Is this a change I need ot make on my website or within the stripe dashboard?
summer mural
The stripe dashbaord is where you go to adjust the events that endpoints are listening to.
You can start on this page of your dashboard, and then click on a specific endpoint to get to its settings:
https://dashboard.stripe.com/webhooks
light aurora
OK- I found that. It's just weird because evertying has been working for years with these endpoints and I haven't made any changes.
summer mural
Hm, well the endpoint that is consistently failing seems to be returning 404 responses to our requests. Maybe that endpoint got moved or decomissioned.
light aurora
Interesting..