A fix has been implemented.
The issue was caused by a human error during the deployment of new guardrail settings for the system. As a result, chat history was inadvertently included in all guardrail checks. Since some bot responses contain JSON characters, the guardrails incorrectly flagged these as inappropriate, causing them to trigger far more frequently than intended.
This problem affected a small subset of customers. It was dependent on a specific combination of the model in use and t...