#craigrobertwhite_api
stark zenithBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1257391097374707732
đ Have more to share? Add details, code, screenshots, videos, etc. below.
tired comet
Looks like it took around an hour, no?
worldly lotus
The end user might have started a report then an hour in started another, thinking they were stuck. Were they particularly big?
Most times those reports only take at most 30 seconds, although I get that it's EOQ
tired comet
One was fairly sizable and took 1 minute. The other one was small and took an hour, roughly
worldly lotus
That's interesting. Looking at our logs, our client was polling for the status of frr_1PXmWqFAed7s9c7s3uhaWHPp starting at 11:52 and stopped at 12:51. Does the stripe.reporting.ReportRun.retrieve() call get cached on your end?
Ah, that must have been the one that was an hour long
When you say sizable, how big is the dataset? Do you have a date range?
Looking at their email, it would be for the entire month of June
tired comet
I'm not sure. A couple hundred rows by my guess, but that report only took a minute. It was the shorter one that took longer. But I would think these reports could be affected, since they were both request on the first of the month
worldly lotus
I guess what I need to know is why these reports take so long some times. In the past, I was told by support that it was because all the reports get stuck in a queue and get run whenever it's their time. I'm getting emails from customers almost twice a month on reports taking a while and the last time I reached out in May it was because of a supposed bug that got fixed on your guys' end.
tired comet
We don't have a lot of context on the situation with report delays, so it might be worth reaching back out to support and getting an updated status on the delays you experienced