> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/integration-and-data-ingestion/salesforce-understanding-archived-tasks.md).

# Salesforce: Understanding Archived Tasks

#### **What is an archived task?**

An archived task in Salesforce is a task that is moved out of the primary view to improve system performance. Archived tasks are not deleted, they’re simply stored in the background.

#### When are tasks archived?

Salesforce automatically archives tasks when:

* The task is closed and older than one year (365 days) or
* The task has no due date and was created more than one year ago.

These rules help Salesforce manage large volumes of activity data while keeping current records easier to work with.

#### How do archived tasks affect HockeyStack?

* Archived tasks are not available in HockeyStack reporting or journeys. This is due to how Salesforce handles them.
* However, they still exist in Salesforce and can be manually imported by admins by a data re-pull.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/integration-and-data-ingestion/salesforce-understanding-archived-tasks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.