#Kike Copeiro
1 messages · Page 1 of 1 (latest)
Hi there, how can I help?
The scenario is as follows: In Stripe the renewal payment is made correctly, but nevertheless the communication does not reach our Restrict Content Pro plugin correctly. This causes RCP to "not know" and the subscription expires.
Reviewing the events of the webhook I have seen that for the events charge.succeeded and payment_intent.succeeded a Response 200 Ok appears, but also the following message:
"PHP exception: This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate."
Investigating more about the logs, I get the error 429 lock_timeout
I have checked that it had many applications that we do NOT currently use. I have deleted it.
Could the origin of this problem be caused by trying to send the information to all those applications?
If not, how can I make my requests serially or at a lower rate?
Hi there, I can only support if you have a direct integration with Stripe. If you have questions related to a 3rd-party plugin, I'd suggest you to reach out to the plugin developer directly.
I agree @turbid coyote , but in this case, I'm detecting that the source of the problem is occurring in Stripe, therefore I don't think the solution is found "outside" or in 3rd-party plugins, don't think?
question is: How could I avoid error 429 lock_timeout?
Are you using a Restrict Content Pro plugin?
yes
The thing is, it doesn't always fail me. it will fail in approximately 20% of the subscriptions that need to be renewed
Yup, so your plugin should handle the 429 errors.
https://stripe.com/docs/rate-limits#object-lock-timeouts this guide tells about 429 errors if you are interested, but it's the plugin's job to implement the integration right.
and, how can I make my requests serially or at a lower rate from Stripe side?
Since you are using a plugin, it's your plugin making the API request on behalf of you. I'd suggest you to reach out to the plugin developer and share them the doc link that I sent earlier.
and ask them to modify his plugin?
@turbid coyote Am I the first person to report this error in #dev-help with the RCP plugin involved?