#bimal-pandey_best-practices
autumn orbitBOT
đ 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/1390617760085573753
đ 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.
- bimal-pandey_unexpected, 4 days ago, 51 messages
serene kestrel
There's no way to avoid the 24 hours reboot, unfortunately. Did you try implementing the automatic reconnection?
inland remnant
Yes I did
So is reconnecting to the terminal once every 24 hours the best way to handle this? Do people use readers like this? Our kiosk app won't ever be closed, it will remain active even during night, so I was hoping for a more reliable way.
How do other developers handle this?