#phant
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
hello! have you tried advancing the test clock a few more times?
yes i did
does it require to be set 10mins before or something to hit the webhook?
cause i did set it before 10mins and it didnt trigger
can you share the corresponding object id that you're expecting a webhook event for, and what event type you're expecting to see?
inovice.paid
okay, what's the invoice id? it'll have the prefix in_
what's the invoice id that you're expecting invoice.paid to be generated for? it'll have the prefix in_
in_1OhOp2CqhyxGoBc4N4YkRDA6
if i look under webhook attempts in https://dashboard.stripe.com/test/events/evt_1OhOp4CqhyxGoBc4st3TrlL8, i see the webhook event is already generated and sent. Your server also successfully received those events
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
why would it be delivered again? I'm not sure i understand the issue here. An event would only be delivered once if your server returned a HTTP 200 response status code
advancing a time clock would not hit the request again?
no, advancing a clock moves the time forward, it doesn't as you put it "hit the request again"
so whats the point of advancing the time clock?
When you use test clocks you simulate the forward movement of time - you can read more about test clocks here : https://stripe.com/docs/billing/testing/test-clocks
and when that time comes(forward set time) wouldnt it hit the webhook again with invoice.paid?
no, it's already been paid
you're moving forward in time
e.g. right now it's 10 pm, you moved the time forward by 1 hour, so now it's 11 pm
the webhook event has already been sent and delivered, there's no reason to resend
so how do i make it act like a subsription?
sorry, but can you explain what you mean by how do you make it act like a subscription?
you can advance the Subscription to the next billing cycle
for example, if your subscription bills on the 7 of every month, if today is 7 feb and that invoice has already been paid, then advance your test clock to 7 mar
your test clock in the screenshot shows that your current simulation time is 7 feb
i want it to be 7th feb
but in minutes ahead
but the webhook did not hit
i cannot wait for a month u know, thats the purpose of test clock
maybe lets step back a bit, the webhook is already sent and delivered for the invoice on 7th feb - do you agree with this?
not backwards
im moving forward itself
okay let me explain it more clerarly
subscription created, invoice was paid at 7th feb - 9.23
please note 9.23
i then advanced the time to 7th feb 10.36
why did not the webhook hit again at 10.36?
thats my question
👋 there
No it's still the same Invoice, and the same Invoice will only send 1 invoice.paid event, no matter whether the time is, as long as it's not retrying
invoice is same?
but the webhook should hit right?
so that i will know that user had paid
Sorry I don't follow the last question. Could you elaborate again?
i have created a invoice meaning i have paid right
so im advancing the time, meaning going for the second payment
am i right?
Which time do you mean for the "first payment" and "second payment" here?
first payment at 7th feb - 9.23 PM
second payment - which is when i advanced my time clock to 7th feb - 10.36 ( which did not hit at all)
yes
but thats the point of using TEST CLOCK right, who would wait till 7th match for testing
i can have it done anytime i want
obviously forward in time, not backward
heyy please i have been chatting for more than 1hour please understand my query and resolve it asap
No the point of Test Clock is to advance the time, doesn't affect the billing cycle
the test clock allows you to move the time till 7th Mar
Of course you won't wait unti 7th March, but you can advance the Test clock past 7th March
That's the point
Yes
thats what i wanted to know, hold on checking after advancing it to 7th march
i advanced it to 7th march
but no event hit except test_helpers.test_clock.ready
If you look at the Subscription page on Dashboard, do you see the event?
The Invoice is still in Draft
Advance it 1 more hour
doing
yes it did hit now
thanks for that, thats what i wanted to know when will it hit and what to do to hit it
Yeah you are welcomed