#rhuzaifa_docs

1 messages ¡ Page 1 of 1 (latest)

fluid baneBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1329032897344311317

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

dusty crest
#

More context. My integration requires

  1. checkout.session.completed to be received and processed before invoice.payment_succeeded with billing reason of subscription_create
  2. invoice.payment_succeeded with billing reason of subscription_create to be received and processed before charge.dispute.created events

ATM I am just adding a timeout/sleep of a few seconds to handle this as I don't want to handle an async queue or add more complex logic to handle out-of-order events.

silk python
#

hi! there is but it can(and has in the past) changed so it's not something we want to explicitly document. It's something like 2/3 seconds for the TCP handshake and then 20 seconds to fully send the response. But that can change at any time and might differ for differnet endpoints.

#

the correct way to handle the case you're describing would be a local queue yes