Combined
Product guide

Sources workspace

Connect context, select datasets, read exact state, operate Runs, review schemas, and delete safely.

A Source is the unit of authorization, ownership, freshness, retention, and deletion. Separate provider tenants are separate Sources even when they use the same connector.

Connect flow

Choose Connect Source, then search or filter the live connector catalogue. Each definition has an exact support badge:

  • Ready can enter the authorization and discovery flow.
  • Preview records an access request for bounded validation; it does not collect credentials.
  • Planned is discoverable but cannot connect.

For a Ready connector, either connect it yourself with your signed-in identity or request authorization from someone who has provider access. Delegated recipients receive a time-bound, identity-bound flow. When authorization completes, discovery returns the provider datasets, fields, supported sync modes, keys, and cursors.

Select the required datasets and fields. Then choose a cadence:

CadenceBehavior
ManualRuns only after an explicit Run action
DailySafe scheduled default
HourlyAvailable only to allowlisted Accounts and enforced by the server

The first Run shows extraction, Delivery, record, and byte progress. A Source becomes fresh only after its data commits to the lake; authorization or extraction alone is not success.

Portfolio and detail

The Sources table reports name, owner, exact state, schedule, dataset/endpoint counts, last success, recent volume, and current issue. Search matches visible Source facts. Open a Source for datasets, fields, logical SQL names, classification, sync mode, selected fields, schema revisions, reviews, and the latest Run.

States

StateMeaning and response
healthyLatest required work committed successfully
syncingA Run is extracting or committing
needs_authorizationAuthorization expired, was revoked, or has not completed
needs_reviewA breaking or ambiguous schema change awaits a decision
pausedScheduling and new manual work are disabled until resume
failedInspect the issue and Activity correlation before retrying
deletingGrants and schedules are revoked; physical cleanup is running
deletedSource is no longer queryable or operable

Actions

  • Run now queues a manual Run. Reuse the same idempotency key after an ambiguous transport failure rather than creating a new request.
  • Pause/Resume changes scheduling and admission without deleting committed context.
  • Request authorization sends a new narrow authorization request to the selected recipient.
  • Schema review accepts or rejects an exact old/new model diff. Additive nullable changes and safe widening do not require review.
  • Delete immediately revokes grants and new work, then queues retention-aware physical cleanup. The confirmation text is required and deletion is not a disconnect toggle.

Use Sources and freshness for checkpoint semantics and Source troubleshooting for recovery decisions.

On this page