#ilya_api
timber hazelBOT
👋 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/1285967037335601235
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
chrome arrow
Hello
first attempt afaik! 🙂 The second time you use the same key, you basically receive the same/cached response from Stripe
timber hazelBOT
grim geode
Hello
first attempt afaik! 🙂 The second time you use the same key, you basicall...
So 24 hour is the cap for all retries, rather than max interval for retries
glad adder
My brain isn't quite parsing the distinction that you are making there but it sounds like you have it. Basically, you use the key for the first time and we associate that key with the response that we sent you and will replay that response when we see that key, after 24 hours we get rid of that association so when we see the key again we create a new association it with whatever new response.
grim geode
Ah, sorry.
By "cap for all retries", I meant - "retryUntil: now + 24h".
By "retry interval", I meant - "nextAttempt: now + retryInterval".
So my question is whether, when I fetched a cached response, it also causes a TTL extension, and apparently it doesn't.
glad adder
Exactly!