#stale_idempotency-retries

1 messages ¡ Page 1 of 1 (latest)

forest sigilBOT
#

👋 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. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 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/1214287572734316544

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

jagged flumeBOT
young umbra
#

@keen flower it depends on the situation and at which point of the request you were rate limited so it's unfortunately tricky to say. But my advice is to use a new idempotency key for those overall since you can be certain the request didn't "happen"

#

stale_idempotency-retries

keen flower
#

Ok thanks. Are there other scenarios / status codes where I would want to use a new idempotency key instead of the same one?

young umbra
#

5xx

keen flower
#

Ok thank you

#

I guess 5xx errors are tricky to handle. The document says "The client can retry the request with a new idempotency key, but we advise against it because the original key may have produced side effects."