#jamie2364

1 messages · Page 1 of 1 (latest)

cedar fableBOT
scenic sapphire
#

Hello, can you send me the ID of a subscription that this happened for?

misty chasm
#

sure. This is the event ID evt_1M9EieHPnYDEIOmwietdwcoi

scenic sapphire
#

Do you have any more recent examples? It looks like past the last 15 days I can't see any errors related to talking to your server

misty chasm
#

chekcing

#

I think the other examples are prior to this though

#

No, there is none more recent. Do you have any idea what might have caused this?

scenic sapphire
#

Gotcha. I can try to search more generally, will see what I can find

#

Do you have the exact text of the error you are getting here?

misty chasm
#

because around this time, other payments were made that successfuly sent webhooks

#

There's no error. This is the problem, you see

#

It just simply doesn't send anything

scenic sapphire
#

These payments sent webhooks, I can see it logged that we sent out events to your endpoints we_1DMhUYHPnYDEIOmwnslY14YX and we_1Ke01MHPnYDEIOmwSGlDVjAr

#

If there isn't an error, is it possible that your server is dropping these events somewhere after it receives them but before it can mark the payment as paid in your system?

misty chasm
#

Do you know what type of situation would cause them to drop?

#

All paypal payments seem to be working fine, that's why I'm slow to think it's a sitewide issue on payments

scenic sapphire
#

Checking to see if I can see any errors that your server sent us back, unfortunately other than that I don't know if I can get much insight in to this without more info. If your server is always sending us 200 codes to acknowledge getting our events then that would mean the issue is happening on your server after it acks the event. So this would have to be something you would want to debug possibly be resending the events and seeing where in the process they get dropped

misty chasm
#

right

#

so you will report back once you cheked?

scenic sapphire
#

Yep doing a query now

#

Would you be able to check if you saw similar issues related to these events on your platform?
https://dashboard.stripe.com/events/evt_1MC09CHPnYDEIOmwUNETGwqu
https://dashboard.stripe.com/events/evt_1MEZWgHPnYDEIOmwUiS2kBWG

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

They seem to have a similar pattern to the evt_1M9EieHPnYDEIOmwietdwcoi event that you sent earlier. Basically the initial attempt to send your server the event failed and we got a generic "internal server error" message from your server. The event was then sent again and accepted

#

So it may be that the server is not properly handling the event when it receives it a second time.

misty chasm
#

Yes, there are some commonalities. For example, the second link is showing that the users subscription has expired, even though it seems like he is paid up to date

#

and the other one also had access issues

#

However, these two issues showed that the webhook was sent. But there were errors. The one I showed you first had no errors and no evidence that it was even sent in the first place

scenic sapphire
#

I can see logs on our side that both of your servers confirmed with a 200 response that they got that webhook event. It sounds like something there may be preventing these successful deliveries from being logged.