Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

550030: Sync extract limit exceeded


ERROR: 550030

error-550030 page anchor
DATA SOURCES
ERROR

The sync operation stopped before completion because the number of records extracted during this run exceeded the per-sync extract limit. The limit protects system stability and prevents runaway syncs from consuming excessive resources. Records beyond the limit were not synced and must be captured in a subsequent run.

Possible causes

possible-causes page anchor
  • The dataset's underlying table or query result set has grown significantly since the last sync, so a single run now tries to extract more rows than permitted.
  • A full resync was triggered on a very large dataset that exceeds the per-run row limit.
  • Incremental filters are missing or mis-configured, causing the entire table to be re-extracted on every run.
  • Add or tighten incremental filters in the dataset's SQL query or configuration—for example, include a WHERE updated_at > :last_sync_time clause—to reduce the number of rows extracted per run.
  • If you must sync the full dataset, break it into smaller datasets that cover disjoint subsets of data (for example, by date range or ID range).
  • Contact Twilio Support to request a higher per-sync extract limit if your use case warrants it.