j7-customer-locks | Stripe Developers | Page 1

opal axle Dec 20, 2021, 6:11 PM

#

hello, that sounds like you might be updating Customers really often and retrieving them too. You can have a look at what requests you're making on the customer object and what GETs you're making to that customer object and maybe space them out more. Retrying is the right approach as well.

unborn lantern Dec 20, 2021, 6:13 PM

#

Is there any relationship between subscriptions or subscriptions schedules and customers? We rarely write to customers but we do make frequent changes to subscriptions and schedules.

opal axle Dec 20, 2021, 6:17 PM

#

there is! when you create or update a Subscription, that grabs a lock on the Customer that the Subscription is for

#

same for SubSchedule too

unborn lantern Dec 20, 2021, 6:20 PM

#

Aha, that makes sense

#

So in general it sounds like a bad idea to retrieve the customer immediately in response to the subscription.updated event

opal axle Dec 20, 2021, 6:22 PM

#

yeah either throw in a delay (or queue up the Customer retrieve calls) or just retry them if you hit a lock timeout

#j7-customer-locks