Data source refreshes
To keep your knowledge up to date, Kapa regularly reruns the source ingestion process.
Data refresh frequency
Different data sources have different data refresh schedules. You can see when Kapa last ingested your sources, and when the next refresh is scheduled, in the Sources view.
The default behaviour is a weekly refresh.
Some sources update more frequently. In the Sources view, this displays as Real-time in the Last ingested and Next refresh columns. The following table shows the update schedules. New content is newly created objects, such as a new JIRA issue or Notion page. Updates are changes to existing items, like comments on an existing issue. Deletions are deletions of entire objects, such as an entire issue or Slack thread.
| Source | New content | Updates | Deletions |
|---|---|---|---|
| GitHub issues | Five minutes | Five minutes | 48 hours |
| JIRA | 10 minutes | 10 minutes | 48 hours |
| Notion | Five minutes | Five minutes | 48 hours |
| OpenAPI | One hour | One hour | One hour |
| Slack | Six hours | Six hours | 24 hours |
| Zendesk helpcenter | 10 minutes | 10 minutes | 10 minutes |
| Zendesk tickets | Five minutes | Five minutes | Five minutes |
These schedules take into account the rate limits of the third party systems.
Slack
Slack has some specific edge cases. The Slack API doesn't allow pulling changes beyond a given timestamp, and has restrictive rate limits.
To work around this, Kapa scans back seven days, every six hours. In other words, every six hours, Kapa checks all threads from the last seven days and checks if anything was added, changed, or deleted.
This means:
- Kapa accurately reflects changes every six hours.
- Kapa can't see changes to older threads. If a thread from eight or more days ago has changes, Kapa won't pick this up.
If you choose to only keep Slack data for a given time period, Kapa deletes threads that fall outside that timeframe every 48 hours.
Review after refresh
By default, after data is reingested, Kapa puts it into review for you to check and approve. Sources awaiting review have a Review button in the Actions column on the Sources view. Once you review and approve the freshly ingested data, Kapa syncs the data to production, and your users can access the information through your Kapa integrations.
Real-time sources don't require review after reingestion. The real-time sources are:
- GitHube issues
- JIRA
- Notion
- OpenAPI
- Slack
- Zendesk helpcenter
- Zendesk tickets