Documentation
Refresh cadence
Refresh is how current your answers are. Cadence is set by plan, and every sync is metered in credits so spend stays predictable.
Cadence by plan
| Plan | Refresh | Data sources |
|---|---|---|
| Free Forever | Manual, weekly maximum | 2, manual upload only |
| Plus | Scheduled refresh | 3 internal sources |
| Growth | Daily automated | 10 sources, 800+ connectors |
| Business | Daily automated | 25 sources |
| Enterprise | Daily on all sources | Custom |
What a sync consumes
| Operation | Credits |
|---|---|
| Connector sync | 1 per source per run |
| Full re-ingest of a source | 10 |
| Manual upload processing | 1 per upload |
| Active seat | 2.5 per active day per seat |
Full credit consumption table lives in the reference section.
When to re-ingest
- You changed the connection scope and need historical rows for the new tables.
- The source system was migrated or its chart of accounts was restructured.
- Entity resolution was corrected in a way that should apply to history.
Refresh FAQ
Can I force a refresh outside the schedule?
Yes. A manual sync can be triggered on any connection, and it consumes 1 credit per source per run.
Does a failed sync consume credits?
A sync that fails before reading data does not count. Partial reads are metered as one run.
How fresh are Risk Alerts?
Alerts are evaluated after each refresh of the sources they depend on, so daily cadence gives daily alerting.
Further reading
Was this helpful?
Contact support