#dishant_webhooks

1 messages ยท Page 1 of 1 (latest)

maiden matrixBOT
#

๐Ÿ‘‹ 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/1220365505685225472

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

unborn spruceBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

unborn wolf
#

here is the time which I advacned to get the webhook events

#

And just for the information I am using CLI for webhook listening for local machine

unborn spruceBOT
feral python
#

Hello

#

Did you advance the time to exactly the renewal date? If so, there is a 1 hour period which the Invoice is in draft before it finalizes.

#

I'd recommend advancing time a bit further and see if you see the relevant Webhooks fire

unborn wolf
#

one subscription I created today that I tried to advance time

feral python
#

Can you share the Subscription ID?

unborn wolf
#

sub_1OwisvKo71sfOhmErAcHlkWJ

feral python
#

Try 8am, needs to be more than 1 hour past the renewal date

unborn wolf
#

okay. I'll try

#

I did 8 am and got these two events only for now
test_helpers.test_clock.advancing
test_helpers.test_clock.ready

feral python
#

Hmm the Invoice is still in draft. Sometimes this stuff can be a bit finicky. Try advancing it by one more day, like to the 29th, and lets see if the Invoice finalizes.

unborn wolf
#

okay I got the payment failed event just now
but why it fails I don't get it

feral python
#

Looking

#

Hmm did you do this for a different Subscription?

#

That one still has its Invoice in draft

unborn wolf
#

no same subscription

#

but the failed events are came late so I updated you accordingly

unborn wolf
#

nope still the invoice is in draft

feral python
#

Hmm okay yeah I see that too. Which shouldn't be the case... I wonder if some of our finalization workers are backed up a little bit right now. Give me a moment to check...

unborn wolf
#

Sure

frigid scaffold
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away soon. I think I have an idea of what could be going on here, and am double checking some timings.

unborn wolf
#

okay

#

can you pls explain that to me

#

if possible

frigid scaffold
#

It looks like invoice.created Events are being sent to one of your webhook endpoints, and when that happens we wait until you successfully respond to those Events before finalizing the Invoice. We will wait for up to 72 hours for that success before proceeding regardless:
https://docs.stripe.com/invoicing/integration/workflow-transitions#:~:text=If we donโ€™t receive a successful response within 72 hours%2C we attempt to finalize and send the invoice

Can you try either adjusting your webhook endpoint so it responds to the invoice.created Events, indicating they were received successfully, or advancing the test clock an additional ~60 hours to try to get past that period.

Learn about invoice status transitions and finalization.

unborn wolf
#

I got the invoice.created and my webhook endpoint just returned 200 in CLI for that event

#

and then nothing happned
I am using CLI for capturing events and running in localhost

frigid scaffold
#

The CLI always successfully acknowledges the receipt of Events. It isn't the endpoint that the CLI hosts that is failing to respond successfully.

#

It is another one of your webhook endpoints.

unborn wolf
#

ohhkk
but is that the case if I am running local machne then that other configured webhook will not triggered?

frigid scaffold
#

No, all Events are always sent to all webhook endpoints listening for that type of Event.

unborn wolf
#

okay that means if one of the webhook endpoint fails then future event is disturbed
Is that correct?

frigid scaffold
#

I'm not sure I'm grasping what "then future event is disturbed" means

unborn wolf
#

that means right now what just happened
like one of the webhook is not delivered successfully so because of that invoice is not finalizing

frigid scaffold
#

Yup, all endpoints will need to indicate that they successfully received the Event.

unborn wolf
#

got it
and as you know that I advanced the time to tomorrow
so can I undo that ?

#

for the same subscription which I shared earlier

frigid scaffold
#

No, you cannot move test clock times backwards, only forwards.

unborn wolf
#

got it
so approx at what time again that invoice.created event retry to success?

#

72 hours
right?

frigid scaffold
#

No, since this is testmode, the Event delivery is attempted 3 times over a couple hours:
https://docs.stripe.com/webhooks#retries
Those attempts appear to have all been triggered and failed. I do not believe that Event will attempt to be delivered again automatically. But you can trigger a resend of that from your Stripe dashboard.

Listen to events in your Stripe account on your webhook endpoint so your integration can automatically trigger reactions.

unborn wolf
#

got it

#

but first my other webhook needs to work for invoice.created

#

I'll check
Thank you
bye