Data Expiration Logic
Cognigy.AI uses the smallest positive TTL value from the following sources:- Management UI Settings. The TTL is set at the organization level via the Management UI.
- Infrastructure Variables. This TTL is set via a server-side environment variable starting with
INSIGHTS_, for example,INSIGHTS_MAX_RAW_ANALYTICS_TTL_IN_MINUTES. - Additional Infrastructure Variables. This TTL is set via server-side environment variables, such as
MAX_CONVERSATION_TTL_IN_MINUTES.
Example
Example
Configuration:
- Management UI TTL = 6 months (262,800 minutes)
- Infrastructure Flag TTL = 1 year (525,600 minutes)
TTL for Analytics Data
Analytics data includes information from the Analytics database: Analytics, Sessions, Step Events, Steps, Conversations collections, and Contact Profiles. The expiration of this data is controlled by environment variables or settings configured in the Management UI. Each value defines how long a specific type of data is stored. Once the configured time is reached, the data is automatically deleted.List of Environment Variables
List of Environment Variables
Examples
Examples
TTL for Conversations
Conversation data in Cognigy.AI expires according to the following data expiration logic:- The system first checks the environment variable:
INSIGHTS_MAX_CONVERSATIONS_TTL_IN_MINUTES. If this variable is set and has a positive value, it takes precedence. - If the
INSIGHTS_MAX_CONVERSATIONS_TTL_IN_MINUTESvariable isn’t set or invalid, it falls back toMAX_CONVERSATION_TTL_IN_MINUTES. - The TTL set in the Management UI is always included in the final check.
- The system picks the smallest positive TTL from the three sources to decide when conversation data expires.
Examples
Examples