> ## Documentation Index
> Fetch the complete documentation index at: https://docs.experio.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Jobs & Monitoring

> Monitor ingestion jobs, flow executions, and system logs

## Jobs

Navigate to **Admin > Monitoring > Jobs** to monitor document processing and ingestion jobs.

### Enrichment Jobs

Enrichment jobs (post-processing rules that enrich the knowledge graph) are managed separately. Navigate to **Admin > Graph > Rules** and use the **Executions** tab to view all enrichment jobs, or open a specific rule and go to its **Jobs** tab. Enrichment jobs support cancel and resume.

### Job List

The jobs page displays a table of all jobs with:

* Job type and name
* Status (running, completed, failed)
* Start and end times
* Progress information

### Starting Jobs

Click **Start New Job** to manually trigger a processing job. This is useful for:

* Initial document ingestion after setup
* Re-processing after configuration changes
* Running one-off processing tasks

### Job Details

Click any job to view detailed information:

* Execution timeline
* Files processed and their status
* Error logs for failed files
* Processing metrics and statistics

### Parse-Only Jobs

Data sources configured with **Ingestion Type: Parse only** run a shortened pipeline that stops after parsing. The job detail page surfaces parse-only mode with several visual affordances:

* **Parse Only badge** — The job header shows an amber "Parse Only" badge next to the scan type. Full ingestion jobs show an indigo "Full Ingestion" badge.
* **Dimmed phases** — The Processing Phases pipeline still renders all six stages, but Classify and Ingest appear dimmed with a "Parse-only mode" caption and a dashed border to indicate they are skipped. A section-level "Parse-only pipeline" badge is shown in the top-right of the card.
* **Parsed status** — Files that complete successfully show a green **Parsed** badge (terminal status `parsed_only`). This is the equivalent of **Ingested** for full-mode jobs.
* **Context-aware file status filter** — The status filter dropdown on the Scanned Files table hides statuses that cannot apply in parse-only mode (Pending Classification, Classifying, Classification Failed, Pending Ingestion, Ingesting, Ingestion Failed, Ingested). All failure variants are consolidated into a single **Failed** option.

## Flow Executions

Navigate to **Admin > Monitoring > Flow Executions** to see the execution history of all automated flows.

The executions page shows:

* Flow name
* Execution status
* Start and end timestamps
* Duration
* Error information (if applicable)

Click any execution to see step-by-step details.

## System Logs

Navigate to **Admin > Monitoring > Logs** to view system-level logs.

### Filtering Logs

| Filter        | Description                                      |
| ------------- | ------------------------------------------------ |
| **Level**     | Filter by log level: DEBUG, INFO, WARNING, ERROR |
| **Search**    | Full-text search across log messages             |
| **Timestamp** | Filter logs by date and time range               |

### Log Entries

Each log entry shows:

* Timestamp
* Log level (color-coded)
* Message content
* Source module

Logs stream in real-time, so you can monitor system activity as it happens.

## Scan Order Statistics

Access scan order statistics from the admin dashboard to review ingestion metrics:

* Number of files discovered per data source
* Files successfully processed
* Files pending processing
* Files that failed processing with error details
* Processing throughput metrics

<Tip>
  Monitor jobs and logs regularly during initial ingestion to catch configuration issues early. Pay attention to files with processing errors — they may indicate content type configuration problems or connector access issues.
</Tip>