Troubleshoot source connections
Use the connection status and most recent activity before changing provider settings. Never paste access tokens, authorization codes, secrets, or private keys into Sentium or support messages.
Administrator approval required
Your organization blocks the application until a Google Workspace, Box, or GitHub administrator approves it. Send the administrator the application name and requested scope shown in the provider's own approval screen. Do not make the folder public or bypass the policy with another account.
Reauthentication required
Provider consent or credentials can no longer be used. Select Reconnect, authorize with a permitted account, and verify the selected scope. Reconnecting does not require unchanged files to be processed again.
Scope lost
The connection still exists, but the authorizing account can no longer read part of the selected folder or repository scope. Restore provider access if appropriate, or update the selection to the intended minimum scope. Sentium records inaccessible items and removes them from current retrieval.
Degraded
Some provider checks failed while the connection remains partly available. Review the affected items and retry after the provider or network condition clears. Do not disconnect solely to clear the status; disconnecting changes the authorization lifecycle.
Processing failed
The source was discovered, but an individual version could not be scanned or parsed. Review the visible reason. Replace encrypted, malformed, unsafe, or unsupported files with an accepted source document rather than converting them through an untrusted service.
Stale
Sentium has not completed a successful provider reconciliation inside the expected freshness window. Use Sync now once. If the state remains stale, check whether reauthentication or administrator approval is required before contacting support.
When contacting support, provide the connection name, provider, visible status, affected file name, and time of the last attempt. Do not include credentials or confidential source contents. See sync and freshness and reconnect or disconnect for the underlying behavior.