Since you referred to the TTL being 24 hours, I am assuming you are referring to the recommendations made via Real-time Containers. Can you explain why do you want to extend the time to live for these records? It would help us understand better if you can elaborate on your business use case/ requirement.
The one obvious downside of extending TTL is that this data will reside on the Decision Data Store (DDS) and if you are having high volumes of inbound container requests then your disk space usage on the DDS storage will start growing up enormously.
As @RaghuShankhawaram mentioned, extending TTL would demand Cassandra Disk space. I would suggest customizing the TTL based on channels (Inbound channels - For Self-service channels, max of 30 mins or equivalent to session timeout, other agent-assisted channels, 30mins-60 mins and for outbound changes based on the feedback loop cut-off time).
Nanjundan Chinnasamy | Pega Lead Decision Architect, 1:1 Customer Engagement
Posted: 4 days ago
Posted: 28 Nov 2023 9:04 EST
Chaitanya Joshi (ChaitanyaJ)