Go back

Ingestion / sync behavior and troubleshooting

Understand how Astell ingests and syncs your data

Why Astell ingests your data

Astell ingests your workspace tools continuously so your information becomes searchable, connected, and actionable in one place. By keeping data up to date across your systems, Astell can surface the right context when you need it, without manual uploads or constant tool-switching. Most syncing is free and unlimited; only specific content types consume tokens during processing.

Sync frequency

Astell syncs data whenever it detects new content or changes in your connected tools. In many cases this happens quickly, but delays can occur depending on the source system and processing load. In the worst case, it may take up to 12 hours for Astell to detect a change and re-ingest the updated data on some sources.

Sync cadence by integration

Sync cadence is managed by Astell per integration. Sources with push notifications, such as Gmail and Google Calendar, update in near real time; other sources sync on schedules ranging from every 30 minutes to a few hours, with periodic safety-net re-syncs on top. You don't need to configure anything for data to stay current.

When an integration breaks

If an integration disconnects or errors, you'll get an email notification. You can usually resolve it by reconnecting the integration. If the problem persists, contact support@labtwofour.com.

Connecting the same service multiple times

You can connect multiple accounts from the same service, for example, two Gmail inboxes or multiple GitHub organizations.

When ingestion happens and how long it takes

Ingestion happens in two cases: the initial ingestion when you first connect a tool, and ongoing ingestion when Astell detects new content or changes afterward. Both run through a queue. In many cases ingestion happens quickly, but delays can occur depending on the source system and processing load, in the worst case, up to 12 hours to detect changes and re-ingest updated data on some sources.

Ingestion priority order

Astell processes ingestion in this priority order:

1. Real-time / recent content
2. User-initiated actions (manual upload)
3. Bulk historical sync
4. Lower-priority background processing

When tokens run low during ingestion

Native Data ingestion continues normally and remains unlimited. Processed Data ingestion may pause, and you'll receive notifications at 75%, 90%, and 100% usage. Ingestion resumes once your tokens reset on the next billing cycle, you increase your token limit (allowing pay-as-you-go), or you upgrade your plan. Anything already ingested remains searchable. Only new Processed Data is affected.