Virtual Agent Microsoft Teams notifications display in Japanese instead of English<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue: When using Now Assist Virtual Agent, provider notifications sent to Microsoft Teams display field values in Japanese instead of the expected language. Cause: Microsoft Teams display field values in Japanese instead of the expected language because a notification script sets `cardHeading` and `cardLinkText` values to NULL, and incomplete records in the `sys_ui_message` table — missing the required Key field — cause the translation process to map those NULL values to the Japanese word. Microsoft Teams display field values in Japanese instead of the expected language because of the below conditions. When a notification script sets cardHeading and cardLinkText values to NULL, the system attempts to translate these NULL values. When incomplete sys_ui_message records exist in the table without the required Key field, the translation process maps these NULL values to the Japanese word. The three mandatory fields for a valid sys_ui_message record are: Key: Internal, case-insensitive unique identifierLanguage: Target language for translationMessage: The translated text displayed to users Records created without the Key field are invalid and cause unexpected behavior. Resolution: Navigate to System Localization > Message Table (sys_ui_message_list.do).Open the list filter by selecting the funnel icon at the top of the list.Add a filter condition: Key — is empty — then select Run.Review the returned records to confirm they are missing the Key field.Select all filtered records and delete them.