---
title: 3.5. Report History
slug: conversation-intelligence/35-report-history
docTags: 
createdAt: 2026-10-24T05:15:32.463Z
---

**Path:** WORK › Report History · **Who:** Agent, Supervisor, Admin

This is the canonical home for job run history. Data Integration links here rather than repeating it.

## Page map

Report History tracks every job run and its outcome — one-off exports from the Analysis List or Test Evaluation, recurring exports, and data import jobs created in **Manage › Data Integration › Job & Schedule**.

| Region / control    | What it does                                                                  |
| ------------------- | ----------------------------------------------------------------------------- |
| Search              | **Search by job name**.                                                       |
| **Job Type** filter | All, **Data Export**, or **Data Import**.                                     |
| **Status** filter   | All, Pending, Processing, Delivering, Success, Partial Success, Failed.       |
| Table columns       | **Job Name**, **Job Type**, **Executed** (timestamp), **Status**, **Action**. |

Reports are also delivered to any destination connector set on the job (for example, email, S3, or SFTP). Connector setup is in [chapter 5](https://docs.exotel.com/conversation-intelligence/5-manage-data-integration).

## Feature hub

### Execution statuses

| Status                         | Description                                                                                                                                                            |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pending                        | Job is queued and waiting to start.                                                                                                                                    |
| Processing                     | Job is actively fetching and processing data from the source.                                                                                                          |
| Delivering                     | Processing is complete; for export jobs, results are being pushed to the destination (S3, SFTP, email). Import jobs pass through this state briefly before completing. |
| Success                        | Job completed successfully — all data was processed and delivered.                                                                                                     |
| Partial Success                | Processing succeeded but some delivery destinations failed (for example, SFTP delivery failed while S3 succeeded).                                                     |
| Failed                         | The run failed. The **Status** filter has a single **Failed** option that covers both failure types below; the status shown in the table tells them apart.             |
| Handler Failed (table status)  | The data processing step itself failed (for example, source unreachable or file format error).                                                                         |
| Delivery Failed (table status) | Processing succeeded but all delivery destinations failed.                                                                                                             |

## Tasks

### View list of exported reports

1. Go to **WORK › Report History**.
2. Search by job name, or set **Job Type** to **Data Export**.
3. Check reports with status **Success** or **Partial Success**.

### Check why a job run failed

1. Go to **WORK › Report History** and set **Status** to **Failed**.
2. Read the status shown in the table: **Handler Failed** points to the source or data (for example, connector unreachable or file format). **Delivery Failed** points to the destination connector.
3. Fix the connector or job in **Manage › Data Integration** ([chapter 5](https://docs.exotel.com/conversation-intelligence/5-manage-data-integration)), then trigger the job again from **Job & Schedule**.

For more causes, see [Troubleshooting](https://docs.exotel.com/conversation-intelligence/8-troubleshooting).