Im working with Azure Health bot Unfortunately in getting this Error "I am sorry, I am no longer available to interact with you. Please try again later or contact support". And I dont know why this is happinng. My Pricing tier is on S1

Hello Taimoor Ali,

Thanks for raising this question in Q&A forum.

I understand that you are encountering the error message "I am sorry, I am no longer available to interact with you. Please try again later or contact support" in your Azure Health Bot, even after upgrading your pricing tier from F0 to S1.

This generic error message is typically a fallback response triggered when the bot encounters an unhandled exception or a critical configuration limit. Since you have already ruled out the message cap (by upgrading to S1), here are the most common causes and troubleshooting steps:

1. Scenario Logic Errors: The most frequent cause is a runtime error within your specific scenario logic.
   • Action: Go to the Management Portal > Language > Models > Scenarios.
   • Open the scenario you were running.
   • Check the Run History or Debug logs. Look for steps that failed (e.g., a failed API call, a variable that is null, or a syntax error in an Action code block).
2. Secret/Keys Expiry: If your bot relies on external data connections or authentication secrets (e.g., for Azure OpenAI, QnA Maker, or custom APIs), and those keys have expired or changed, the bot will crash and return this default error.
   • Action: Check Configuration > Secrets and verify all connected services are valid.
3. Compliance/Privacy Configuration: Sometimes, aggressive privacy settings or invalid terms of service configurations can block the interaction immediately.
   • Action: Review your Configuration > Compliance settings.
4. Throttling/Quota Delays: Although you upgraded to S1, sometimes the provisioning takes a short while to propagate, or there might be a specific "Messages/second" rate limit being hit if you are load testing.

If the logs in the portal do not provide a stack trace, try reproducing the issue in the "Test Webchat" pane within the portal with the Debug mode toggled on. This often reveals the specific step causing the crash.

If helps, approve the answer.

Best Regards,

Jerald Felix