API tokens or access keys might have an expiration time. If the token is valid only for a short duration, the service will stop responding after the token expires. You may need to verify that your application is refreshing the token regularly if required after check the authentication method you're using and ensure it complies with Azure guidelines for long-running services.
Timeout settings on either the client-side (your bot) or server-side (Azure) might be set to a default value (such as 3 minutes), causing the connection to terminate after that time. Review any timeout configurations and see if they can be adjusted.
If you're sending a large number of requests in a short period, you might hit Azure rate limits, causing the service to stop processing requests temporarily.