#hendie_api
inland lotusBOT
đ 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/1446285178841337949
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
pliant breach
Hi there - you're saying that the time to get a response from stripe is sometimes > 7 seconds?
last lynx
yes
this seems to be the pattern for offline terminals. I guess my question is why so long? Do you try to wake the terminal and that takes time, or what. surely you can detect immediately that a terminal is offline, and respond in under a second?
pliant breach
I'm not certain; I'm looking into the stats for this api method on your account over the last week to get an idea of what the baseline is
last lynx
I'm sorry, but I have to step away from my desk. I will check back later what you found, or you can email me at hendie@mytime.com please.
inland lotusBOT
autumn berry
Hi @last lynx, I'm taking over your thread from my colleague. I looked at req_6Edt2FflRgBxVb with my team and we agree that there's a possibility this request may have taken longer than expected to complete. We will raise this to the relevant team and we're happy to work with you async over email on this. To do this, I will drop you a DM to create a support case with us. When you're back, please check your DM and follow the instructions there to create the support case.
Unfortunately we can't send users email directly. As our Discord channel is also public, you may want to remove your email address if you're concern about sharing it publicly.