#Mike-reporting
1 messages · Page 1 of 1 (latest)
Hi! Please give me a few minutes to look into this.
Another option could be to simulate that event with the Stripe CLI https://stripe.com/docs/cli/trigger
And could you share your webhook endpoint ID (we_xxx), so I can check that it is correctly configured?
Hi @brazen torrent
That event isn't available using trigger; none of the reporting events are
I'm 99% sure it's configured properly, as I've been testing it manually
Thanks, I'm having a look.
And when were you expecting to receive the reporting.report_type.updated event?
That's my question really. From the docs:
A reporting.report_type.updated webhook is sent as soon as a new day’s data is available for a given report type. The payload includes the updated ReportType object. You’ll typically receive 20-30 webhooks each day, two for each report type. (Different users are eligible for different reports.)
It's a bit vague. It sounds like it happens if you have the event registered for the webhook (I do) but it's not clear if it works for test mode or if you need to schedule the reports somehow.
In any case, I've had my test webhook registered for reporting.report_type.updated over night and saw no such event.
Thanks for the clarification! I agree this is not super clear in the documentation. I'm currently trying to reproduce this on my end.
We made some tests, and we didn't manage to get a reporting.report_type.updated event sent in test mode. So it looks like this only works in live mode. We will need to clarify the documentation about this.
Sorry about the confusion!
I see, that's frustrating
As general feedback to your product people, I'd say that too much of your reporting infrastructure only works in live mode. That leaves me having to go live without knowing whether all my machinery is going to work properly!
I gave up on Sigma for the same reason
Anyway, I'll mock and test as best as I can and hope I've nailed it.
Thanks for your help
I understand, sorry about that. I'll make sure to share that feedback internally!