# Automatic expiration of Task search results

**URL:** <https://community.perplexity.ai/t/automatic-expiration-of-task-search-results/2353>\
**Category:** Feature Requests\
**Tags:** sonar-api\
**Created:** [October 29, 2025, 12:03pm UTC](https://community.perplexity.ai/t/automatic-expiration-of-task-search-results/2353 "2025-10-29T12:03:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wmnf1989](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/wmnf1989/32/1603_2.png) [@wmnf1989](https://community.perplexity.ai/u/wmnf1989)\
**Post date:** [October 29, 2025, 12:03pm UTC](https://community.perplexity.ai/t/automatic-expiration-of-task-search-results/2353/1 "2025-10-29T12:03:27Z")

</div>

## 🚀 Feature Request

I’d like to suggest that Perplexity add an option to automatically expire Task search results after a selected period (e.g., 7, 30, or 90 days), allowing these results to be deleted from history or Library without impacting the underlying Tasks or their recurrence.

## 🔍 Problem Statement

Currently, search results are stored indefinitely, which can clutter the workspace and make management difficult—especially for frequent users or those running recurring/long-term projects.

## 💡 Proposed Solution

Introduce a parameter to set result expiration time when creating a Task or through global service settings. Results would be deleted automatically after the set period, while the Task itself remains active to generate new results.

## 📌 API Impact

- This affects Threads and Library-linked features. It’s relevant to search, chat completions, and search filter modules. Implementation would likely require a new setting, both in user interface and API endpoints.

- **Model affected:**  
Applicable to all Tasks, regardless of the underlying model, including Sonar Deep Research.

- **Required new parameters:**  
Yes, this would require an extra parameter for result expiration.

## 🔄 Alternatives Considered

Manual deletion is possible today, but this can be labor-intensive and doesn’t scale well for organizations or heavy users.

## 📎 Additional Context

This would add value for individuals and teams, promoting better organization while aligning with privacy and data management best practices.

* * *

---

<div class="post-metadata">

**Author:** ![Kesku](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/kesku/32/898_2.png) [@Kesku](https://community.perplexity.ai/u/Kesku)\
**Post date:** [October 30, 2025, 12:50pm UTC](https://community.perplexity.ai/t/automatic-expiration-of-task-search-results/2353/2 "2025-10-30T12:50:44Z")

</div>

This forum is focused on the **developer community** (API, integrations, and technical issues), not core product features or app suggestions.

For feature requests like this one, please share your idea directly in the **official Perplexity Discord server** instead:

👉 [discord.gg/perplexity-ai](https://discord.gg/perplexity-ai)

---

<div class="post-metadata">

**Author:** ![Kesku](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/kesku/32/898_2.png) [@Kesku](https://community.perplexity.ai/u/Kesku)\
**Post date:** [October 30, 2025, 12:50pm UTC](https://community.perplexity.ai/t/automatic-expiration-of-task-search-results/2353/3 "2025-10-30T12:50:47Z")

</div>

Closed on October 30, 2025, 12:50pm UTC


