Run slices let you scope a pipeline run to a date or key window — the same operational pattern Fivetran and Airbyte use for backfills, without giving up ownership of generated code. In eltPulse, a slice value is passed as partition_key into generated dlt or Sling pipelines.
date, updated_at) and strategy.partition_values per trigger.The builder and run-slices page show a capability badge per source: date/key slice wired, full replace only, or not yet wired. Tier-1 connectors in the catalog are held to a high bar — either honest slice support or an explicit "full replace only" label.
eltPulse picks the right mechanism per connector family:
start_date, since, or env-bound incremental cursors (e.g. HubSpot, Salesforce, Personio).update_key + incremental mode on the stream.since or cursor.Verified sources with production slice wiring are tracked in codegen; the UI reads the same registry so labels stay in sync with generated Python.
Pipeline declarations accept _partitionConfig in sourceConfiguration — same shape as the run-slices editor. See Pipelines for POST /api/elt/pipelines/declaration.