Issue Summary

As described in Rovo data, privacy, and usage guidelines, Rovo won't be usable in HIPAA (and other) compliant instances. When trying to use Rovo Chat, customers will see We're not sure of what went wrong message, engaging them to try again after a reload:

Reloading the page won't change the behavior.

This can also be confirmed when checking the Browser Network tab, where an error similar to this one is going to be observed: 

{
    "errorMessage": "Browsing product has hipaa enabled. product=jira",
    "errors": [
        "convoai.rest.browsing.product.has.hipaa.enabled"
    ],
    "statusCode": 403
}

These same customers may also experience some confusion when visiting their Rovo instance directly, where they can interact with the Rovo, even Rovo Chat. Still, they won't see results from their HIPAA (and others) compliant instances.

Expected Results

When Rovo is enabled, visit Rovo Chat and see one of these experiences:

• An improved error message stating in the UI the instance has regulatory requirements, frameworks, guidelines, or other types of restrictions;

And/or when visiting Rovo directly see a banner or some type of warning message an instance from the organization has regulatory restrictions and results won't show up. 

Actual Results

When Rovo is enabled, visit Rovo chat and receive a generic error message screen due to regulatory requirements, frameworks, guidelines, or other types of restrictions;

Workaround

There is no known workaround for this behavior. When available, a workaround will be added here.