bennie-webhook

[hardy jungle]

Do you mean when will stripe retry the webhook?

[proud frost]

yeah

[hardy jungle]

1. Stripe uses the exponential backoff logic https://stripe.com/docs/webhooks/best-practices#retry-logic;
   It is a smart retry and it depends on a lot of factors
2. each event will contain a next_attempt information on https://dashboard.stripe.com/test/events

[hardy jungle]

hi Bennie, I am still here

what is your question? are you asking if that is the retry time?

[proud frost]

"Period_end" assignment error

[hardy jungle]

what do you mean by that?

what error are you seeing?

[proud frost]

"Period_end" assignment error，should be 1632552663

[hardy jungle]

I don't quite understand what you mean.

what event are you looking at and why you think it should be 1632552663?

[proud frost]

please check “il_1Jd8UrD56xuafeEIrvYwJo33”

The two values are exactly the same

[hardy jungle]

can you share the invoice id?

in the format of in_xxxxx

[proud frost]

in_1Jd8UrD56xuafeEILA9UwhbE

the two values are subscription start time and end time

[hardy jungle]

Yeah, that looks like a bug; but to get the subscription start / end date, you should use the subscription.current_period_start and subscription.current_period_end instead

let me feed back to the team

[proud frost]

I want to add the original metadata of the "invoice.paid"

[proud frost]

When will it be resolved, I am waiting for this feature

[proud frost]

hi , Are you there

[hardy jungle]

The team might need to take some time to resolve this. What feature are you trying to implement and any reason that you cannot leverage subscription.current_period_start and subscription.current_period_end instead ?

[proud frost]

i need confirm subscription time.

[hardy jungle]

subscription.current_period_start and subscription.current_period_end should serve the purpose of getting the subscription billing cycle. you don't really need to use the invoice.

[proud frost]

ok