---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/intelligent-experiences

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Trobleshooting

# Troubleshooting for Conversation Improvement Themes {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Troubleshooting steps for errors that might occur in Conversation Improvement Themes.
Scenario/Symptom: The dashboard is not showing any data, one week after the install.

Associated Error Codes/Warning: N/A.

Steps to Resolve:

Make sure all the skills and scheduled jobs are active by following the steps given in [Activating Conversation Improvement Themes](https://servicenow-prod.fluidtopics.net/CjyOP95yU_5aRo1jQ4Jbrg "Activate the Conversation Improvement Themes application to analyze conversation quality.").
Scenario/Symptom: Execution staging records are stuck on Processing/Failed.

Associated Error Codes/Warning: Flow-related logs in syslog.

Steps to Resolve:

Increase flow logging (preferably in dev).  
Environment guidance:

* Dev/Test: Set verbose logging to All configurations and runtime value.
* Prod: Use Runtime states and duration only. Don't enable All configurations and runtime value in production.
{#conv-impr-themes-ts__ul_xy2_djb_jhc}  
Steps:

1. Navigate to Process AutomationFlow AdministrationProperties.
2. Set Level of reporting data generated by the flow engine to the appropriate level (see the guidance above).
3. Create a conversation through the Portal and end the conversation.
4. Navigate to Process AutomationFlow DesignerTheme Tagging(subflow) or Primary Request Tagging(subflow).
5. Review flow executions. Identify any actions marked Failed or Error and address the cause.
6. If all actions are Complete and there is no other path indicating failure handling, open a Support ticket.
{#conv-impr-themes-ts__ol_a1x_fjb_jhc} Scenario/Symptom: Execution staging records Failed when default model is Gemini/Claude/Now LLM.

Associated Error Codes/Warning: Skill Execution timed out.

Steps to Resolve:  
This is a known issue with Gemini and Claude as they are slow thinking models, responses may be slow and sometimes can get timed out. To resolve this, reduce the chunk size in system properties by performing the following steps:

1. Navigate to AllSystem Properties (sys_properties.list) and search for sn_na_thematic.dataChunkSize and reduce it. The ideal chunk size for all the models is:
   * Azure Open AI: 100
   * Gemini: 25
   * Claude: 5
   * Now LLM: 1
   {#conv-impr-themes-ts__ul_fwp_bmb_jhc}
2. Move the failed Execution staging record to processing.
{#conv-impr-themes-ts__ol_m5t_wlb_jhc}  
Generative AI Logs: If an evaluation is not complete, navigate to sys_generative_ai_log and check for the following definitions to see if there are any errors:

* Theme Extraction
* Themes Update Definition
* Themes Primary Request Tagging
{#conv-impr-themes-ts__ul_pld_gmb_jhc}

Outbound HTTP:

If no Gen AI logs are created, check the Outbound HTTP logs for any issues exist.

Sys Logs: Check sys logs for any errors related to passing with scope as sn_na_thematic.