---
title: "View message run history"
slug: "view-message-run-history"
description: "Analyze message run history and errors in Connectivity Studio. Review processing details and troubleshoot issues effectively."
tags: ["Task topic"]
status: "update"
updated: 2026-10-05T12:07:43Z
published: 2026-10-05T12:07:43Z
canonical: "docs.staedean.com/view-message-run-history"
---

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

# View message run history

You can review and analyze the history of message runs.

### Steps

1. Click **Connectivity studio - Integration operations**.
2. The **History errors** tab shows the message run history records with errors.

On the **History errors** tab, find and select the desired message run from the list.

> [!NOTE]
> **Note**
> 
> You can view the full message run history on the **History** tab.
3. Click **History**.

> [!NOTE]
> **Note**
> 
> You can also open the message run history from several other places, for example, the **Connectivity studio - Integration design** workspace and the **Message** page.
4. Review and analyze the message run history.

In the **General** section, you can find, for example, information on the related project and task.

In the **Processing** section, you can find information on record processing, such as the number of records with errors, the number of processed records, and the number of updated records.

Close the page.

> [!NOTE]
> **Notes**
> 
> If no records are processed, no errors are reported either. This can be caused by:
> 
> - The document record range: A document range limits the records that are processed. So, if no records are processed unexpectedly, verify the document record range.
> - Message mapping conditions and field conditions: Conditions limit the records that are processed. So, if no records are processed unexpectedly, check whether conditions are defined for the message on the record mapping or field mapping.

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>