adys

[quaint dagger]

👋 happy to help

[random hemlock]

req_3bWhynNaReCjc9
req_dIaOcFw8YTvqUU
req_5l4EsaXvkLPLWk

[quaint dagger]

taking a look please hold on

I'm starting to think this might be eg. one of the connected apps (intercom, chartmogul…) trying to access the data and not their code causing the error?
I actually can't really tell but it could be one of the possibilities

it's really not easy to pinpoint what's causing this without having access to the code

but a good way to check is basically checking the webhook endpoints code, that sometimes can possibly include some retrieval API calls

[random hemlock]

Yes we have some retrieval on webhook and those are what's directly causing it, but the lock itself it's hard to tell what it's caused by

[quaint dagger]

what are you trying to achieve in your webhook? would you mind sharing your code?

[random hemlock]

@quaint dagger the webhook is powered by dj-stripe. it's watching over a variety of event types; it gets the object, puts it in the db, and sometimes makes additional requests to related objects present in that object to also sync them to the db

read only operations

[quaint dagger]

while a subscription is being updated

I think you need to reach out to dj-stripe and let them know

[random hemlock]

im the maintainer of dj-stripe 🙂

[quaint dagger]

they might need to change the way they handle those events

[random hemlock]

yeah we are, but this is the only time I've seen this cause issues for a user

so i think something is different for them

[quaint dagger]

do you happen to know which event types are causing this issue?

[random hemlock]

so … im not sure if it's specific event types causing the issue; because it's hard to tell. when looking at the logs, I can filter by status failed and method GET, and look at the 429s. i see it's requests to invoices and customers indiscriminately

[quaint dagger]

what are the types of events that you listen to?

would you mind listing all?

[random hemlock]

i actually don't think I have access to tell on that account. acct_1IVDi9El9AVRLibq if you want to take a look

[quaint dagger]

isn't that done in your code though?

[random hemlock]

i have read/only and it seems like i cant inspect existing webhooks using it

dj-stripe handles almost every type of event

but this customer doesn't listen to every type of event

we used to do it because, Once Upon A Time, stripe had less event types and it was manageable lol

dev says it's mostly these three causing it: customer.updated, invoice.payment_succeeded, invoice.paid

[quaint dagger]

yes I was going to say that

there's no reason to listen to both of these invoice.payment_succeeded, invoice.paid

invoice.paid is enough

especially if you're doing retrieval in both

depending on what you're doing customer.updated might also cause issues

[random hemlock]

ok im gonna recommend to disable invoice.payment_suceeded, let's see if it helps. but customer.updated we need to keep listening to.

and you have no visibility on what is actually causing the locks?

[quaint dagger]

no I don't unfortunately

[random hemlock]

thanks. we disabled payment_suceeded, let's see.

[quaint dagger]

yes let me know if you need any more help