Zurück

How far back Astell ingests your data

Each plan's indexing window, how the rolling window works, and the Slack thread edge case.

How far back each plan indexes

Each plan indexes a different depth of history (the "indexing window"): Astell processes data within that window, and older content falls outside it.

• Sapling: 3 months
• Tree: 18 months
• Grove: 60 months (5 years)
• Forest (Enterprise): customizable

A longer window means more of your historical context is searchable and available to your loops.

How the rolling window works

Each plan's indexing window is a rolling window measured back from today, not a fixed calendar date. On Sapling, for example, Astell indexes roughly the last 3 months of history, and as time passes that window moves forward with it. Ingestion runs continuously (how often depends on the integration), and on each pass Astell looks back across the window from the current moment, so new content that falls inside the window is picked up automatically.

Data you have already ingested

Once content has been ingested it stays in your workspace and remains searchable, even after it ages past the rolling window. The window governs what new content Astell pulls in; it does not delete what you have already indexed.

How edits and replies re-enter the window

Most integrations stamp each item with a last-modified (or last-updated) time. When you edit a document, comment on an issue, or update a record, that timestamp moves forward to the moment of the change, so the item falls back inside the rolling window and is re-synced on the next pass. That is why activity on older items is normally picked up with no extra steps.

The Slack thread edge case

Slack is the known exception. Slack identifies a message, and a thread, by the timestamp of when it was first posted, and that timestamp does not change when someone later replies. Astell reads Slack history by that original timestamp, so a reply added to a thread whose first message is older than your indexing window is not picked up, even though the reply itself is recent. Example: a Slack thread started 4 months ago and replied to today stays outside a 3-month window, because the thread's first message is still 4 months old. Messages already ingested are kept. Other integrations avoid this because their items carry a last-modified time that moves forward on each change; Slack messages do not.