Runtime Issue “Sorry, looks like something went wrong. Let’s try that again.”

Question

Runtime Issue “Sorry, looks like something went wrong. Let’s try that again.”

cs admin 0

we are experiencing a issue at different times. Our health bot encounters a runtime error during use, displaying the message, “Sorry, looks like something went wrong. Let’s try that again.”

I initially assumed it was related to a limit or something else, but this issue is occurring on the S1 tier.

Anonymous

2026-02-09T09:23:46.8966667+00:00

Hi cs admin

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.

Thank you!
Anonymous

2026-02-10T12:34:43.38+00:00

Hi cs admin

Did you get any chance to review the above response.

Thank you!
Anonymous

2026-02-11T10:35:43.87+00:00

Hi cs admin

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
cs admin 0 Reputation points

2026-02-12T10:57:02.4566667+00:00

Unfortunately, the provided solution didn’t resolve my issue, I’m still struggling with it.
Manas R Mohanty 17,270 Reputation points Moderator

2026-02-12T14:00:39.1566667+00:00

Hi cs admin

Could you help with details requested in private message.

Thank you.
Manas R Mohanty 17,270 Reputation points Moderator

2026-02-16T13:36:15.9266667+00:00

Hi cs admin

Could you help me with documentation used for creation of Health bot service.

I went with Health care agent resource for testing as discussed in this thread and could not locate S1 tier on resource. rather found a C1 tier for Agent instead.

Thank you.

Your answer

Anonymous

2026-02-09T09:23:46.8966667+00:00

Hi cs admin

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.

Thank you!
Anonymous

2026-02-10T12:34:43.38+00:00

Hi cs admin

Did you get any chance to review the above response.

Thank you!
Anonymous

2026-02-11T10:35:43.87+00:00

Hi cs admin

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
cs admin 0 Reputation points

2026-02-12T10:57:02.4566667+00:00

Unfortunately, the provided solution didn’t resolve my issue, I’m still struggling with it.
Manas R Mohanty 17,270 Reputation points Moderator

2026-02-12T14:00:39.1566667+00:00

Hi cs admin

Could you help with details requested in private message.

Thank you.
Manas R Mohanty 17,270 Reputation points Moderator

2026-02-16T13:36:15.9266667+00:00

Hi cs admin

Could you help me with documentation used for creation of Health bot service.

I went with Health care agent resource for testing as discussed in this thread and could not locate S1 tier on resource. rather found a C1 tier for Agent instead.

Thank you.