christian-blackburn_api | Stripe Developers | Page 1

errant grottoBOT May 27, 2025, 12:08 AM

#

👋 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/1376713644850544640

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

rancid fulcrum May 27, 2025, 12:10 AM

#

hello! gimme a while to take a look!

dim comet May 27, 2025, 12:11 AM

#

Thanks!

rancid fulcrum May 27, 2025, 12:22 AM

#

https://dashboard.stripe.com/events/evt_1RSsxzCPODlSNewZlgEkkyDQ - the reporting.report_run.succeeded was created

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.

#

it doesn't seem like your webhook endpoint is listening for that event though?

dim comet May 27, 2025, 12:23 AM

#

No, this is run in a different part of the code, so we poll for the status

#

Which is why we only poll for 5 minutes, we didn't expect the report to take 18 minutes to produce

#

We are doing this because retrieving the risk_reserved_funds via other APIs seems to take a while as we have to go through so many pages

rancid fulcrum May 27, 2025, 12:25 AM

#

ah okay, so here's the thing, there's no timeframe for when the report will finish generating. It's also why it's typically better to listen for the reporting.report_run.succeeded webhook event instead

#

i've seen reports take as long as half an hour sometimes

#christian-blackburn_api