Zurück

Ingestion/sync behavior and troubleshooting

Understand how Astell ingests and syncs your data

Why does 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 switching between tools. Most syncing is free and unlimited, and only specific content types consume tokens during processing.

How often does data sync?

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 8 hours for Astell to detect a change and re-ingest the updated data.

Can I control sync frequency?

Yes. You may choose real-time, hourly, daily, or manual on-demand. See docs/integration-and-data. Grove Plan

What happens if an integration breaks?

If an integration disconnects or errors, you'll get an email notification. You may resolve it by reconnecting the integration (See docs/integration-and-data). If the problem persists, contact founders@labtwofour.com.

Can I connect the same service multiple times?

Yes. You can connect multiple accounts from the same service, such as two Gmail inboxes or multiple GitHub organizations.

When is data ingested, and how long does ingestion take?

Ingestion happens in two cases:

• (1) the initial ingestion when you first connect a tool, and
• (2) ongoing ingestion when Astell detects new content or changes afterward.
  Both initial and ongoing ingestion are processed 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, it may take up to 8 hours for Astell to detect changes and re-ingest updated data.

What's the ingestion priority order?

• Real-time / recent content
• User-initiated actions (manual upload)
• Bulk historical sync
• Lower priority background processing

What happens 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 additional pay-as-you-go usage), or you upgrade your plan. Anything already ingested remains searchable — only new Processed Data are impacted.