# Replay Apica's **Replay** feature allows you to send previously ingested logs to a configured destination (e.g., S3 bucket, Splunk HEC endpoint) even if those logs were not mapped to a destination at the time of their ingestion. Replay allows selective resending of logs to the desired destination by user-defined criteria such as time range and attribute match. Replay especially comes in handy when there is an investigation of a historical incident, where a subset of logs can be sent to a destination.
### How it works: 1. A [forwarder](/flow/list-of-forwarders.md) must be configured that sends the logs to the desired destination.

2. Navigate to the explore page and select the namespace-application whose logs must be sent to a destination.

3. Hover over the Ellipsis button, placed above the list of namespace-applications. Once the dropdown appears, click on the *Replay* option.

4. Upon clicking the **Replay** option, a **Replay Configuration** modal will appear. Here, you can select logs from different namespace-application pairs along with their ingestion time range. In the **Forwarder** column, choose the configured forwarder from the dropdown menu.

5. Additionally, a filter expression can also be added to send only a subset of logs for that particular time range.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apica.io/flow/replay.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.