Monitoring Tab

Understand what each status means, why files land there, and what to do about it

This article contains:

• How monitoring works
• The status cards
  • Synced
  • Processing
  • Failed
  • Unsupported
• Supported file types & size limits
  • Supported file types
  • Size limits
  • Other content limits
  • Rate limited
• The "Summary" panel
• The "File Details" table
• Quick FAQ

How monitoring works

Every file we discover in your connected source (SharePoint, Egnyte, OneNote, etc.) moves through an ingestion pipeline. As it moves, we record its current status. The Monitoring page groups your files by that status so you can see, in real time, what is searchable, what is still in progress, and what could not be ingested.

At a high level, files split into:

• Supported files — file types we can ingest, which end up Synced, Processing, or Failed.
• Unsupported files — files we cannot ingest (wrong type, too large, corrupted, password-protected, etc.). They never block your sync.
• Rate limited — files we could not yet retrieve from the source because it throttled us. These are not yet classified — once we successfully fetch the file, it will resolve into one of the buckets above (Supported → Synced/Processing/Failed, or Unsupported).

The status cards (top row)

Synced

What it means: The file was fully processed and is now searchable in AlphaSense.

• This is the successful end state. A file counts as Synced only after content extraction and indexing both complete.
• The 100% · 0.21 GB line shows how much of your supported files have reached this state.

Do I need to do anything? No. This is the healthy, finished state.

Processing

What it means: The file has been picked up and is moving through the ingestion pipeline (downloading, converting, extracting, or indexing), but hasn't finished yet.

• Newly added or recently updated files sit here temporarily.
• Large files, or large batches, naturally take longer.

Do I need to do anything? No — just wait. Files here resolve to Synced on success, or to Failed / Unsupported if the file can't be completed. If a file stays in Processing for an unusually long time, it will be automatically re-checked and reclassified.

Failed

What it means: The file is supported, but processing did not complete because of an error in the pipeline or a downstream service.

• These are typically transient / system-side issues (indexing errors, temporary service errors, delivery delays, storage upload errors, etc.), not problems with your file itself.
• Most failures are retried automatically by the platform.

Do I need to do anything? Usually no — these are retried on our side. If a file remains Failed for an extended period, contact AlphaSense support with the file name/ID.

• What kinds of issues land here? (internal error codes)

  Code	Meaning
  ER101	Integration service error
  ER102	Invalid / malformed payload from connector
  ER402	Indexing error
  ER501/ER601	Ingestion pipeline error
  ER505	Document storage upload error
  ER801	Search pipeline delay

  These codes are internal and shown here for support reference only.

Unsupported

What it means: The file cannot be ingested and has been skipped. This is a permanent state for that file as-is — nothing is wrong with the platform.

• Common reasons: unsupported file type, file too large, too many pages, empty file, corrupted file, password-protected, unsupported (unicode) characters in the name/path, file cannot be converted, file not found at source, or access not granted.
• Unsupported files are not counted against your supported-file total and never block the rest of your sync.

Do I need to do anything? Only if you want that file searchable. Depending on the reason, you may be able to fix it at the source (e.g. remove the password, convert to a supported type, reduce the size/page count, rename to remove special characters, or grant access) and re-sync. See Supported file types & size limits below for the rules.

Common "Unsupported" reasons (internal skip codes)

Supported file types & size limits

Whether a file is Supported or Unsupported is decided by two checks up front: its type (extension) and its size. Files that pass both flow into the pipeline; files that fail are skipped with a specific reason (see the code table in Unsupported).

Supported file types

We can ingest the following formats. Anything outside this list is marked Unsupported → Unsupported File Type (SK02).

Size limits

Each file type has a maximum size. Files above the cap for their category are skipped as Unsupported → File Too Large (SK03). Limits differ by category:

Other content limits

A supported, correctly-sized file can still be skipped if it breaks one of these content rules:

Rate limited

What it means: The source system (e.g. SharePoint/Microsoft) temporarily throttled our requests, so we could not yet retrieve these files.

• This is temporary and automatic — the platform backs off and retries later on its own.
• It reflects source-side throttling, not an issue with your file or configuration.
• Rate limited is not a final verdict. Until we successfully fetch the file from the source, we don't yet know whether it's supported. Once retrieved, a rate-limited file resolves into one of the other buckets — it may become Synced, sit in Processing, land in Failed, or turn out to be Unsupported.

Do I need to do anything? No. Rate-limited files are retried automatically; each will be re-classified once the throttle clears and we can read it.

The "Summary" panel

The donut and the three rows below it recap the same data at the file-portfolio level:

The "File Details" table

The search box plus the status chips (Synced, Processing, Failed, Rate limited, Unsupported) let you filter the file list by any of the statuses defined above. Use it to:

• Search for a specific document by title or file ID.
• Filter to a single status (e.g. show only Unsupported files to decide which to fix).
• Track a file's progress as new data is automatically synced.

Quick FAQ

Q: My file is "Failed" — did I do something wrong? No. Failed almost always means a temporary, system-side issue that we retry automatically. Unsupported is the category tied to the file itself.

Q: Why is my supported-files percentage below 100%? Some files are still Processing or temporarily Failed, and some may be Rate limited (not yet retrieved). Processing/Failed files aren't guaranteed to become Synced — depending on the content they may resolve to a permanent Failed or Unsupported state.

Q: My file type isn't in the supported list — can I still ingest it? Only if you convert it to a supported format first (e.g. export to pdf or docx), then re-sync.

Q: Will unsupported or rate-limited files block my other files? No. Each file is tracked independently; skipped or throttled files never hold up the rest of your sync.

Q: How fresh is this data? The page shows the last refresh time at the top right. Use Refresh to pull the latest.