What is the query limit for related records, and what are the new data sync limits in Appian?
Answer
Appian has three limits that are easy to mix up: the Data Sync row limit, the related record limits, and the Sync Records smart service limit. They apply to different things.
1. Data Sync row limit per record type
Data Sync copies data from a database or supported external service into Appian’s own data service, so record queries, grids, and interfaces don’t hit the source every time. The maximum rows per synced record type depends on the capability tier, not just the software version.
Capability tier | Max rows per synced record type |
|---|---|
Standard | 4 million |
Advanced | 20 million |
Premium | No set row limit |
Performance and infrastructure requirements still apply to large datasets.
Example: A telecom support app has 6 million tickets, of which 1 million are active or recently closed and 5 million are historical. On Standard, the full table exceeds the 4 million row limit.
Configure a sync filter so only active and recently closed tickets sync, and handle the historical ones separately, for instance with an archival record type that uses direct data access.
2. Related record limits
For one-to-many relationships, a!relatedRecordData() lets you filter, sort, and limit the related records returned with each base record. These limits apply per base record, not to the whole dataset.
Function | Default related records | Maximum |
|---|---|---|
| 10 | 100 |
| 10 | 100 |
| 100 | 250 |
Example: A customer has 150 support tickets. When you list several customers with a!queryRecordType(), you get up to 10 tickets per customer by default, and you can raise that to 100. When you open one customer with a!queryRecordByIdentifier(), you can retrieve up to 250. To get the latest 20 tickets:
This is illustrative. The relationship and field references must match your application.
Retrieve only the related records the interface needs. If you need more than the maximum, run a separate paginated query against the related record type.
3. Sync Records smart service
The Sync Records smart service syncs specific records by their unique identifiers. It accepts at most 1,000 identifiers per request. That applies to the smart service and a!syncRecords(), not to the size of the record type.
Example: an external telecom system changes the priority of 2,500 tickets, and you want those changes in Appian without a full sync. Split the identifiers into three batches of 1,000, 1,000, and 500, and loop over the smart service in a process model. For a service-backed record type, you also need to configure a Sync by Identifier expression.
4. Salesforce API usage during sync
When Salesforce is the source of a synced record type, Appian documents one Salesforce API call per 1,000 rows synced. Syncing 25,000 customer records therefore takes about 25 calls (25,000 ÷ 1,000). That is an estimate for the sync itself, and other operations may use more calls. If the Salesforce API quota runs out, the sync can fail, so plan the sync to fit within it.
5. Other sync limits
Operation | Limit |
|---|---|
Scheduled incremental sync | 50,000 rows per run |
Incremental sync execution | 10 minutes |
Full sync execution | 4 hours |
Auto-sync, flat CDT with a Data Store Entity write | 50,000 rows |
Auto-sync, nested CDT with a Data Store Entity write | 1,000 rows |
Fields in a synced record type | 100, including custom fields |
The CDT limits apply only to automatic sync after Data Store Entity operations. Example: if a billing system updates 80,000 invoices before the next scheduled incremental sync, that exceeds the 50,000 row limit for one run. Sync smaller sets more often, or use a batch-based integration design.
Official Appian Documentation
Check yourself
Question 1 of 4, on what the answer above covers.
- 1.What is the maximum number of rows per synced record type on the Standard capability tier?
- 2.A Standard-tier app has a Ticket table with 6 million rows, but it only needs active and recently closed tickets. What is the best way to stay within the sync limit?
- 3.Question 3 of 5You call a!queryRecordType() and use a!relatedRecordData() to raise the related record limit. What is the maximum number of related records returned per base record?
- 4.An external system updates 2,500 tickets. The Sync Records smart service accepts up to 1,000 identifiers per request. What is the minimum number of requests you need?