Rate-limit handling
Last updated 2026-06-14
Definition
Rate-limit handling keeps a busy source from breaking your whole sync. Every external API caps how often you may call it. When a connector nears that cap, Quri backs off and retries rather than hammering the source, and skips what it cannot read this round instead of failing everything — degrading gracefully so the rest still updates.
How to do this in Quri
- Connect your sources at /app/connect as usual.
- Let Quri pace its requests to stay within each source’s rate limit.
- If a source throttles, Quri backs off and retries on the next sync.
- Check source health at /app/connect to see what synced and what was skipped.
Frequently asked
- What happens when a source hits its rate limit?
- Quri stops pushing, waits, and retries later instead of erroring out. It skips what it cannot fetch this round, so a throttled source does not take your other metrics down with it.
- Will rate limits make my data incomplete?
- Only briefly. Skipped reads are picked up on the next sync once the limit clears. Quri favors finishing the rest now and catching the remainder soon over failing the whole run.