Skip to main content

Ingestion Queue

The Document Processing Queue on the Sources Dashboard shows documents that are actively being processed or have failed ingestion. Admins can retry failed documents without leaving the dashboard.

Location: /sources/dashboard → Document Processing Queue section

Ingestion queue showing Failed tab with one failed document and Retry button

Queue tabs​

TabDescription
Failed NDocuments that failed ingestion. Retry is available.
Waiting NDocuments currently queued for the backend to process.

Queue table columns​

Both tabs share the same column layout:

ColumnFailed stateWaiting state
Document IDUUID link → document detail pageUUID link → document detail page
SourceSource code link → source detail pageSource code link → source detail page
Last UpdateTimestamp of last failed attemptTimestamp of when Retry was clicked
AttemptsCount of failed ingestion attemptsNumeric count (represents retry queue entry)
ActionsRetry button (icon)Empty — no actions while waiting

Retry a failed document​

  1. Navigate to /sources/dashboard.
  2. In the Document Processing Queue, ensure the Failed tab is selected.
  3. Locate the failed document row.
  4. Click the Retry button in the Actions column.
  5. The document immediately disappears from the Failed table.
  6. The Failed counter decrements and the Waiting counter increments in real-time.
  7. Switch to Waiting to confirm the document is now queued.

No page refresh is needed — the counter update is synchronous.

Queue after Retry: Failed counter shows 0, Waiting counter shows 1 Waiting tab active showing the document now queued, no Retry button in Actions column

Empty states​

StateMessage
Failed tab, zero items"No failed documents" — grid not shown
Waiting tab, zero items"No documents waiting for processing" — grid not shown

State transitions​

Failed (Attempts: N)
  → [Retry clicked]
  → Waiting (Last Update: now)
  → [Backend processes — succeeds]
  → Removed from queue

  OR

  → [Backend processes — fails again]
  → Failed (Last Update: now, Attempts: N+1)

Business rules​

RuleBehaviour
Retry moves to WaitingImmediately; no page refresh needed
Queue counts update in real-timeFailed/Waiting counters reflect the change synchronously
Last Update updates on RetryShows the time Retry was clicked, not the original failure time
No Retry in Waiting stateActions cell is empty while the document is queued
Attempts valueDisplayed for both Failed and Waiting states
Document ID is always a linkNavigates to /sources/{sourceCode}/{documentId}