---
title: "Sync Status & Troubleshooting"
description: "Check connection status, and spot and fix sync failures"
canonical_url: "https://meingpt.com/en/docs/integrations/data-pools-rag/troubleshooting"
language: en
---

# Sync Status & Troubleshooting

How to tell whether a data pool is syncing cleanly, and what to do when it isn't. Setup and configuration of a data source: [Data Sources & RAG](/en/docs/integrations/data-pools-rag).

## Connection status

Each data source shows a status dot for its current connection state:

| Status | Meaning |
| --- | --- |
| 🟢 Ready | Connected and syncing regularly. |
| 🟠 Not ready | The connection exists, but the last sync failed or was incomplete. |
| 🔴 Unreachable | The source could not be reached during the last check. |
| ⚪ Unknown | Status has not been determined yet (e.g. right after creation). |

Common causes of **Unreachable** for a single data source:

- The source's access token (e.g. SharePoint, Google Drive, Confluence) has expired or was revoked
- Permissions were revoked in the source system
- Network or firewall changes on the source system's side
- For an Outpost data source, the status reflects reachability from MeinGPT's side - it can differ from the Outpost's own local indexing state. If the Outpost console shows the folder fully indexed but MeinGPT still shows Unreachable or Unknown, check the Outpost's own connection display for the underlying cause.

If all of your data sources show "Unreachable" at the same time — including sources with completely different underlying systems (e.g. SharePoint, Google Drive, and Confluence simultaneously) — this usually does not point to a problem with the individual sources, but to a temporary platform-side issue. In that case, contact MeinGPT support instead of reconnecting individual sources.

## Monitor sync status and fix failures

Every data pool syncs automatically every 15 minutes. If a sync fails, you can see it and fix it directly in MeinGPT.

### Automatic alert email

Admins automatically get an email when there's a problem with a data pool:

- **Sync failing** – a data pool has failed to sync several times in a row. New or changed documents stop being indexed until this is fixed.
- **Data source connection lost** – an OAuth connection (e.g. SharePoint) repeatedly fails to refresh its access token.
- **Spike in sync errors** – an unusually large share of files errored out during a sync.

Each email links directly to the affected data source in your settings. You can toggle these notifications individually under **Settings → Notifications → Outpost alerts**.

### Check sync status

1. Open **Settings → Data sources**
2. Click the affected data pool
3. The **Sync Logs** tab has two sub-tabs: **Runs** shows recent sync runs as a numeric summary, **Logs** shows the error message for each individual file

Each row in the **Runs** sub-tab has three numeric columns:

| Column | Meaning |
| --- | --- |
| Found | How many files this run found in the source - the full listing of the configured scope, not just new or changed files |
| Ingested | How many of those found files were actually processed and added to the index during this run |
| Errored | How many files failed during this run |

**These three numbers apply only to that one run**, not cumulatively to the whole data pool - they reset to 0 at the start of every new sync run. Two consecutive runs can therefore show very different values without that indicating a problem. For the total number of currently indexed files, see [Indexing progress](/en/docs/integrations/data-pools-rag/search#indexing-progress) at the top of the detail page instead.

If the **Errored** count is above 0, switch to the **Logs** sub-tab, filter by **Status** = `error`, and open the affected row - the **Message** column contains the exact error for that specific file, for example a note about a metadata field that could not be processed. That message is the starting point for troubleshooting; if it doesn't make clear what to do, contact [support@meingpt.com](mailto:support@meingpt.com) with the exact wording.

### Manually trigger a resync

1. Open the affected data pool under **Settings → Data sources**
2. Click **Re-Synchronize** to start a new run immediately

Every sync run – whether automatic or manually triggered – also removes entries for files that have been deleted from the linked source. A manual resync is therefore the right way to clear out stale index entries without having to recreate the data source. In rare cases, a single deletion may be missed during the sync and will still be present after a resync – if that happens, reach out to MeinGPT support so we can look at the affected data source directly.

### Re-authenticate the connection (OAuth sources)

1. Open the affected data pool under **Settings → Data sources**
2. Click **Reconnect** and authenticate again
3. Your existing source settings stay unchanged — only the authorization is refreshed

If that doesn't help, contact [support@meingpt.com](mailto:support@meingpt.com).

### "Could not verify account" during initial setup

This message can appear the very first time you connect an OAuth source, before any sync has run - usually because the Microsoft or Google sign-in window closed without returning a valid authorization code. For SharePoint, the most common cause is missing admin consent for the MeinGPT application in your Microsoft tenant; details and other causes: [SharePoint/OneDrive troubleshooting](/en/docs/integrations/sources/sharepoint#troubleshooting).

## Next up

### [Search & Answers](/en/docs/integrations/data-pools-rag/search)

How search works, release levels, citations, and the 3-stage model.

### [Formats & Access](/en/docs/integrations/data-pools-rag/formats-and-access)

Supported file formats, emails and attachments, access control.

### [Data Sources & RAG](/en/docs/integrations/data-pools-rag)

Back to the overview: setup and configuration.