#reginbald_api

1 messages · Page 1 of 1 (latest)

cunning kestrelBOT
#

👋 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/1222105053255700501

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

wet stag
long tangleBOT
wet stag
#

Code in the stripe go library that should retry HTTP code 409

quiet raptor
wet stag
#

Should I then increase the MaxNetworkRetries from 2 to a greater number?

#

I'm only seeing the 409 error

cunning kestrelBOT
sharp carbon
#

What is the intention of firing simultaneous requests with the same idempotency key?

wet stag
#

They idea is that in the unlikely case that two requests to create an invoice is made for a single order then Stripe would only create a single invoice

#

Our system will automatically send Stripe a request to create an invoice but a user can also trigger that request

sharp carbon
#

That's not really what idempotency keys should be used for. They're to safely retry any requests where the outcome was unknown

#

What you describe is something you'd generally handle in your application logic, to prevent the additional n requests for the invoice