Data Expiration¶
The Data Expiration (TTL, time-to-live) displays the time span until the Insights data expires.
To see, when the data will expire, click 
in the upper-right corner of the current page. To view the value in minutes, hover the cursor over the current value.
When you use Cognigy products daily, the data expiration values won't change because each new data update resets the countdown to expiration.
Data Expiration Table¶
Deprecation of Understood Messages
With Cognigy.AI 4.91, the Understood Messages concept was deprecated. The shutdown date is June 2025. Use the Goals and Tasks concepts to evaluate whether your AI Agent understood a particular phrase.
Refer to the list of all upcoming removals on the Deprecations and Removals page.
In the table below, you can view the data included in TTL.
| Data | Description | reports/Explorers |
|---|---|---|
| Analytics | This shows the time span between the creation of all Analytics data and its deletion from the database. | Overview: - Number of Inputs - Top Intents - Understood Messages - Understood / Misunderstood Messages Engagement: - Avg. Session Length - Max. Session Length NLU Performance: - Avg Intent Score - Average Execution Time - Intents by Score Range - Max Intent Score - Understood Messages - Understood / Misunderstood Messages - Top Intents - Top Intent Scores |
| Conversations | This shows the time span between the creation of chat history analytics and its deletion from the database. | Transcript Explorer, Message Explorer |
| Sessions | This shows the time span between the creation of Insights session analytics and its deletion from the database. | Overview: - Active Sessions - Positive Ratings - Sessions - Session by Channel - Total Sessions - Top Goals - Top Slots - Unique Contacts - Users by Locale Engagement: - Contacts - Goals Reached - Handovers by time of the day - Live Agent Escalations - Positive Ratings - Positive Ratings over Time - Top Goals NLU Performance: - Top Slots |
| Step Events | This shows the time span between the creation of Step data and its deletion from the database. | Step Explorer |
| LiveAgentEscalation | This shows the time span between the creation of Live Agent data and its deletion from the database. | Live Agent |
| voice-gatewayEvents | This shows the time span between the creation of Voice Gateway data and its deletion from the database. | - |
| GoalsV2Events | This shows the time span between the creation of Goals data and its deletion from the database. | Goals |
Activate Data Expiration¶
By default, Cognigy.AI keeps Analytics, Steps, and Insights Session data to a maximum of 1 year. You can set a shorter data expiration period the Management UI. To do so, follow these steps:
- For on-premises installations and dedicated SaaS installations, set limits in the Management UI.
- For shared SaaS installations, contact Cognigy technical support and specify the limits in your request.
If you have already set limits in the Management UI, the Data Expiration indicator automatically appears in Insights.
The Data Expiration feature applies only to new data obtained by Cognigy.AI after activating Data Expiration in the Management UI. Any datasets obtained before setting the expiration value remains unaffected from this change.
For example:
You set a 1-minute expiration value at 13:00 for Sessions in the Management UI.
All Sessions created after 13:00 will automatically expire after 1 minute due to the 1-minute expiration date set in the Management UI.
Sessions created before 13:00 will remain unchanged.
Change Data Expiration¶
For on-premises Cognigy.AI installations, you can adjust data expiration durations via the management-ui. For SaaS installations, contact technical support.
When you adjust the data expiration value, it will only apply to new data obtained by Cognigy. The expiration value for previously obtained data will remain unchanged.
Customize Data Expiration for Multiple Organizations¶
If you manage multiple organizations, you can customize the Data Expiration settings for each organization independently through the Management UI.
The default Data Expiration is set in the environment variable in the values.yaml file.
Note
Specifying the Data Expiration for a specific organization in the Management UI overrides the environment setting for that organization. This setup ensures tailored Data Expiration configurations per organization, balancing global defaults with organization-specific needs.