> For the complete documentation index, see [llms.txt](https://docs.feedotter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedotter.com/automations/features/sending-history.md).

# Sending History

Review the complete history of automation runs, including successful sends, skipped sends, and errors.

The Sending History pop-up is one of the best tools for troubleshooting automation behavior and understanding what happened during a specific automation run.

### Access Sending History

To view the history for an automation:

1. Navigate to the **Automations** tab in the Feedotter UI. 
2. Locate the automation you want to review.
3. Click the **three-dot menu** in the Actions column.
4. Select **View History**.

<div align="left" data-with-frame="true"><figure><img src="/files/spQ8AEDSTwojnUcB0Skg" alt=""><figcaption></figcaption></figure></div>

A history window will open displaying all runs associated with the selected automation.

### Understanding the History View

Each history record represents a single automation run.

<figure><img src="/files/9Wl1YXvsnpQnbww5SORP" alt=""><figcaption></figcaption></figure>

For each run, Feedotter displays:

* Preview of the generated email
* Date and time of the run
* Number of new posts detected
* Number of posts included in the email
* Link to the generated email in your ESP
* Status of the run

### New Posts vs Included Posts

The **NEW/INC** column displays two values:

**New Posts**\
The number of articles Feedotter identified as new during the automation run.

**Included Posts**\
The number of articles ultimately included in the generated email.

### View Emails in Your ESP

If an email was successfully generated, the **ESP** column includes a link to open the email directly within your connected Email Service Provider.

This can be useful when reviewing generated emails, troubleshooting sending behavior, or verifying content.

### Understanding Statuses

The **Status** column displays the result of each automation run.

#### Success

A **Success** status indicates that Feedotter successfully generated the email and completed the automation process.

#### Problem

A **Problem** status indicates that Feedotter encountered an issue during the automation run.

When a problem occurs:

1. Click **View Details**.
2. Review the error information provided.

The details window contains specific information about the failure and is often the fastest way to determine what went wrong.

> **Need help?** If you're unsure how to interpret an error message, review the troubleshooting documentation or contact the Feedotter team at [**success@feedotter.com**](mailto:success@feedotter.com) and include the error details.

### Viewing Skipped Runs

By default, skipped automation runs may be hidden from the history view.

To display skipped runs:

1. Open the Sending History window.
2. Enable the **Skipped** checkbox in the upper-right corner.

Feedotter will display runs that were skipped because automation conditions were not met.

Common reasons for skipped runs include:

* No new content was found
* Require New Content to Send was enabled
* Content did not meet filtering requirements

Skipped runs will display a status of **Skipped**.

### Automation Details Page

You can also review automation history from the **Automation Details** page by clicking the automation name from the Automations table.

The Automation Details page displays a visual history of previous sends, including full email previews (click the eye icon) and quick access to generated emails.

For more information, see [**Automation Details**](/automations/automation-details.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.feedotter.com/automations/features/sending-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.