Hi Chiranjeet,

                 Let me explain why this behavior happened. In Pega, we try to always ensure data availability even when DDS service is not available. In order to do so, whenever a read operation happens for a materialized summary dataset, the following behavior occurs:

We read the materialized aggregate and its timestamp and the timestamp of the last customer interaction. This happens at the customer's level:

• If the timestamp of the last interaction is later than the timestamp of the aggregate (which means there are more data that needs to be aggregated) we go to the relational DB to read the Interaction history data and read all the interactions between these two timestamps and add them to the materialized aggregate and return the result to the customer. Otherwise, we return the materialized aggregate directly.

• If the Cassandra read operation fails, then we read all the Interaction History records from the relational DB for the given time window and return the aggregated result to the customer. Obviously, in your case this is what happened. 

Hope that helps, please let me know if you have further questions!