#ctro_webhooks
lilac lindenBOT
đ 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/1378045792639520929
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sinful tinsel
hey vegvisir, thank you
for additional context: https://litcharts.prod.litcharts.com/subscriptions/webhook is no longer active but litcharts.com is.
And it looks like the unsuccessful webhooks to litcharts.prod.litcharts.com are keeping the subscriptions from renewing
hexed mirage
yes, the disbaled webhook endpoint is keeping the invoice from finalizing.
sinful tinsel
does that mean we need to delete that endpoint entirely?
or is there something we can do to force those invoices to hit the other endpoint
hexed mirage
Yes, I think deleting would ultimately solve the issue. But let me doublecheck what I can find
Is it possible that, you disbaled the enpoint on your server and then disabled the enpoint on our end, so that the event might have been send out inbetween? Which would explain the failed attempts.
sinful tinsel
yeah, that is indeed possible. in fact, I think that is what happened.
but we're talking about hundreds of these events
10s of thousands of dollars
so we're looking for the best way to retry all of them
hexed mirage
Got it. So when you delete an endpoint on your server but not in the Stripe enviroment, we obviously will still try to deliver enabled events to that endpoint. As soon as you disable the endpoint also on our end, we will also stop retrying the event.
https://docs.stripe.com/webhooks#automatic-retries
sinful tinsel
that is understood. and I appreciate that you understand the issue. what we're looking for now is the solution
we already disabled the new endpoint
hexed mirage
Ok cool. Just wanted to make sure.
Generally you have the option to simply wait for about 72h after Invoice creation, because we will then finalize the Invoice automatically. If don't want to wait that long, or you can't wait that long you can expedite the process by follwing this guide: https://docs.stripe.com/webhooks/process-undelivered-events
sinful tinsel
should we also delete the already-disabled webhook endpoint
before running through that guide?
also, won't retrying those events just retry them at the already-disabled endpoint? which we can not and don't want to use
can we just force them to finalize instead:
https://docs.stripe.com/api/invoices/finalize
?
hexed mirage
If you simply retry the event delivery, it might also retry the disabled endpoint which won't help finalizing the Invoice obv. But you can also "manually" finalize the Invoice using the doc you are mentioning
sinful tinsel
OK, so it sounds like you have low confidence that retrying might work
lilac lindenBOT