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

# Run history

> Every report run is recorded, scheduled or sent by hand, so you can see what went out, who received it, and why a delivery failed.

Every run is recorded, whether it went out on its schedule or somebody sent it by hand, so you can see what actually went out rather than guessing.

* **History** in the header of the **Reports → Schedules** page shows every run across all your schedules
* Each schedule's own page shows its last three runs in the sidebar, with **View history** for the full list

Each entry records when the run happened, which schedule and report it was, the delivery channel, what set it going, and how many rows it contained.

The **Outcome** column tells you what happened:

| Outcome               | Meaning                                                                                                                     |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Delivered**         | The report was sent                                                                                                         |
| **Nothing to report** | The run found no rows, so nothing was sent                                                                                  |
| **Not delivered**     | The delivery failed - hover the info icon for the reason, usually a disconnected account or a channel that no longer exists |
| **In progress**       | The run is still being generated                                                                                            |

## Run details

Click any row to see everything recorded about that run: when it was generated and delivered, how long it took, the channel, the row count, and the failure reason if there was one.

It also lists **who it was sent to**, exactly as it was at the time. That is the quickest way to settle "it says delivered but nobody got it", because the recipients on the schedule may have changed since.

## What triggered a run

The **Trigger** column separates the two ways a report goes out:

* **Schedule** - the run happened on its cadence
* **Manual** - somebody used [Send now](/user-guide/reports/scheduling#send-now); the run details name them

## Filtering and export

You can filter by schedule, report, outcome and channel, and search by schedule name or error. Tick the rows you want and export just those, or export everything matching your filters, as CSV, Excel, XML or JSONL. The export carries more than the table shows, including the full recipient list and the raw error text, which is what you want when you are digging into a delivery problem.