Connector troubleshooting
Resolve sign-in, source access, synchronization and processing errors without widening permissions unnecessarily.
Start with the connection, not a full reimport
- 1Open the connector
- 2Read status and last sync
- 3Check the failed job details
- 4Repair the specific cause
- 5Retry and verify one document
A saved configuration is not proof of a healthy connection. A successful connection test is not proof that every selected file can be processed. Check both connection health and the result of the last synchronization.
Sign-in and credentials
| Message | Cause to check | Action |
|---|---|---|
| Invalid client / expired client secret | Wrong client ID, secret value or expired secret | Update the app credentials, save, then reconnect |
| Invalid grant / authorization no longer valid | Revoked or expired consent/refresh access | Start Connect again in CogLake; do not reuse an old callback link |
| Access denied | User source access or missing consent | Ask the appropriate source/app administrator; do not grant write rights unnecessarily |
| Invalid scope | Wrong permission type or unavailable requested scopes | Compare the provider setup guide and obtain required consent |
| Redirect mismatch | Callback differs from the provider registration | Copy the exact displayed callback including scheme, host and path |
| Session expired | Stale or parallel connection attempt | Start once from CogLake and finish in the same signed-in browser |
| Rate limited / provider unavailable | Provider capacity or temporary outage | Wait, then retry; repeated reconnects usually do not help |
For Microsoft apps, use the secret value, not its secret ID. For Google Drive, check the consent audience and testing status in the setup guide.
SSH / SFTP
| Message | Safe solution |
|---|---|
| Missing/invalid host fingerprint | Obtain the verified SHA256 fingerprint from the server administrator |
| Host key mismatch | Verify whether the server key legitimately changed; never disable verification |
| Authentication failed | Check user and password/key |
| Invalid private key | Use the supported unencrypted PEM private key, kept only in the credential field |
| Path not found / permission denied | Verify the root and read/traverse permissions with the server owner |
| Symbolic link / outside root | Choose a real directory inside the configured root |
| Timeout / unavailable | Check host, port and network reachability, then retry |
Many files skipped
Skipped does not necessarily mean failed. Files can be unchanged, unsupported, excluded by scope or otherwise not eligible. Inspect the job's message and document details. Use a known supported file to verify that a changed document really updates. Do not force a full import solely because an incremental run processed few files.
Connected but nothing in search
- Finish all setup steps and save.
- Check that scope includes the expected folder.
- Confirm a sync has actually run.
- Inspect any processing failure for the file.
- Check CogLake role access and original source permissions.
- Search for a distinctive phrase after processing finishes.
Retry safely and report
Open Diagnostics, select the job and inspect affected documents. Retry only the relevant failed processing where available. If repeated attempts fail, share the time, connector name, job reference and safe error message with support. Never share tokens, passwords or private keys.