@Neminath In CDH 24.2, pxResponsesStream is a Pega Stream dataset backed by the platform’s stream service, and it gets a record every time CDH serves an action to a customer through inbound containers, web widgets, call center, or an outbound run. The channel execution writes the response event, and out-of-the-box data flows read that stream to persist Interaction History and build IH Aggregates. Think of it as the real time pipe that transports response events, not the system of record. The data typically includes customer ID, action, treatment, channel, eligibility and timestamps, and later gets enriched with outcomes. Retention on pxResponsesStream is short and operational, usually days rather than months, because long term history lives in the IH tables. On Pega Cloud it is commonly around a week and is managed on the stream topic, not in rules. You can confirm the exact value in Admin Studio under Stream by checking the pxResponsesStream topic. If you need a different window, request a stream retention change or add a downstream persistent dataset and keep IH purging aligned with your compliance policy.