#stripe-connect-platform_webhooks

1 messages ยท Page 1 of 1 (latest)

forest galeBOT
#

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

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

ocean mapleBOT
trail hearth
#

Unfortunately the exact data on what we sent is gone. I think I can still look up what HTTP code your server sent us back though

#

Actually to be clear, are you saying the events should have gone to a webhook on the accounts themselves rather than your platform account?

copper sparrow
#

Nope

#

Right now it looks like Stripe sent no webhook

#

I really would love Stripe to show 1 year of logs. Hiding anything but the lasy 15 days makes debugging issues like this basically impossible. ๐Ÿ˜ฆ

#

Customer just emailed me Monday. Events are from Feb 13th, a month ago. That is typical. Hiding all the data just totally hobbles us. ๐Ÿ˜ฆ

#

Not sure how to resolve this customer issue longterm.

#

If you let me know if we sent a 200, that helps a little I guess but I have to figure out why we sent a 200 and did not remove the customer's access. If you give me the data packet, I can do that, but if you delete/hide it, I'm not sure how to assist our customer. ๐Ÿ˜ฆ

#

I'll send Stripe support a request to maintain longer logs I guess.

It would really be helpful. The way it is now just makes it impossible to debug issues. It used to not be this way, no? I feel like I used to have this data available and now it has disappeared. We've been doing this app since 2016.

#

OK, well if the data is irretrievable, I best move on. Thank you.

celest magnet
#

Yeah data is gone, but I can see the result of the webhook conversation

#

Both those events were sent to 3 endpoints successfully

#

All responded with 200s

copper sparrow
#

OK, but how would i know why we didn't successfully process it without being able to get the data exactly as it was sent?

#

OK, is there a place in Stripe where I can put a request to show longer history and maintain this data?

#

Or just Stripe support?

celest magnet
#

No our event retention policy is fixed unfortunately

#

But event retention is last 30 days, not 15 to be clear

ocean mapleBOT
copper sparrow
#

Attempts to send this event to connected platform endpoints in the past 15 days

celest magnet
#

Ah the webhook conversation, yeah

copper sparrow
celest magnet
#

But you'll have access to the exact event object for 30

copper sparrow
#

I don't understand.

#

Are you saying that via an API call, I can retrieve back 30 days but via the dashboard only 15?

celest magnet
#

No via the dashboard you have access to the full event data for 30 days as well

copper sparrow
#

So one of the events happened Feb 17th, today is March 13, can I get the data sent ?

celest magnet
#

Webhook conversation is different

#

That's 15 days

#

If you go to the events page and filter by the event id you will still see the entire event object for 30 days

copper sparrow
#

I am not sure what an events page is. I am looking at the event details for customer.subscription.deleted.

#

How do I see the event data packet sent to our connect platform?

celest magnet
#

If you scroll up it will show the event object

#

We don't show a "data packet"

#

But you can see the full event object

copper sparrow
#

evt_1ObK0AJXgu5c6jhQgFgeUrDO

celest magnet
#

Under Event data

celest magnet
#

So you can't

copper sparrow
#

But the object under "Event data" is not the same object sent to our connect platform. Different structure.

#

If there is a bug in the code and we run the event data object through it, it will fail since it is designed to process the exact format of the data not some other object

low yarrow
#

Hi, taking over as Pompey needs to step away. Let me catch up here

copper sparrow
#

OK I think the solution is for Stripe to please not hide data older than 30 days. ๐Ÿ˜ฆ

#

OK, I have to resolve this issue and need to go do that. I understand your policy and that it makes it not possible to resolve in the easy fast and simple way I would love to resolve if you maintained this data for me. But you do not so I have to find a different solution. Have a great day. Thank you.