Source troubleshooting
Recover authorization, discovery, schema review, ingestion, pause, deletion, and freshness problems.
Open the Source detail first. Its current state, issue action, latest run, schema reviews, and Activity usually identify the next safe operation.
needs_authorization
The provider grant is missing, expired, revoked, or invalid. Start Authorize again from the Source or create a Source authorization request for the correct owner. Do not paste a provider secret into support chat. After authorization, wait for discovery state before queuing repeated runs.
If an authorization request expires, create a new request. Its URL is time-bounded and should be sent only to the intended recipient.
Discovery does not complete
Check the authorization request status for discoveryState and discoveryError. Confirm the provider account can list the desired resources, required connector fields are present, and provider rate limits allow discovery. Avoid creating parallel authorization requests for the same intended change.
needs_review
A discovered schema differs materially from the accepted revision. Review added, removed, renamed, type-changed, and classified fields. Accept only when downstream queries and grant scope remain appropriate; reject with a concise reason to retain the previous accepted schema. Queue a run after the decision if the UI does not do so automatically.
failed
Inspect the latest attempt and delivery evidence in Activity. Correct credentials, provider permissions, connector configuration, or a connector-specific known limit before using Run now. Repeating an unchanged failure can consume provider quota without improving freshness.
paused
Pause intentionally stops scheduled ingestion. Resume the Source, then queue a manual run if immediate freshness is required. A paused Source can still have queryable committed snapshots, so disclose its old lastSuccessAt when using the data.
Stale but healthy
Compare lastSuccessAt with the expected schedule and freshness threshold. A Source can remain operational while a slow or empty run is still within policy. If the expected time has passed, inspect Activity, then queue one manual run. Do not infer freshness from row values alone.
Deleting or deleted
Deletion is asynchronous. deleting means cleanup was queued; wait for Activity to report completion. deleted Sources cannot be resumed or reauthorized. Connect a new Source if data should be ingested again. Uninstalling Desktop or revoking provider access is not a substitute for completing the governed deletion workflow.
Desktop Sources
For permission_required, grant the named OS permission and restart the app. For offline, check network access and system time. For revoked, start a new enrollment. The full state guide is in Desktop capture.