Suddenly receiving "Sorry, looks like something went wrong. Let's try that again" - how to resolve this?

Question

Today our HealthBot application stop working - the error in the conversation logs within Healthbot/HealthCare Agent Services reports "Sorry, looks like something went wrong. Let's try that again" as the error message.

The only clue I find as to what is going on is within the Scenario Manager - if I "Edit Steps" and then select "Run from Here", I see that a "timeout of 3000ms exceeded" is reported under the Trace tab. This implies something wrong when communication with the resource server, which appears to be :

https://hbstenant2steausprod.z13.web.core.windows.net

No outage is reported but I was curious if there's another way to troubleshoot this problem or report it. Thank you in advance.

Answer 1

Hi Rob,

Thank you for the update, and I appreciate the detailed observation.

It’s likely that the issue you encountered was caused by resource limitations or transient backend issues affecting the F1 (free-tier) HealthBot instances. The F1 tier operates on a shared, non-guaranteed compute model, which can occasionally experience service degradation during periods of high traffic or backend maintenance.

Since your S1 (paid-tier) instances remained unaffected, this further suggests that the issue was isolated to the free-tier infrastructure. These tiers typically have lower performance guarantees and may experience throttling or timeouts under load, especially when backend traffic is elevated.

While the issue resolved without intervention, it’s possible the platform rebalanced resources or restarted the affected service nodes overnight.

To avoid such disruptions in production or business-critical scenarios, we recommend using the S1 tier, which provides:

·       Dedicated compute resources,

·       Higher reliability and performance,

·       Better SLA support.

If this behavior recurs or causes operational impact, we also suggest:

·       Enabling Application Insights to trace timeouts and response latency,

·       Subscribing to Azure Service Health alerts for proactive monitoring.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you!