# Monitor transactions
Source: https://www.stedi.com/docs/edi-platform/operate/transaction-data

***

title: Monitor transactions
sidebarTitle: "Monitor transactions"
------------------------------------

You can monitor, inspect, test, and debug the transaction data flowing through Stedi.

## Filter and sort

You can review all incoming and outgoing transaction data on the [**Files**](https://portal.stedi.com/app/core/file-executions) and [**Transactions**](https://portal.stedi.com/app/core/transactions) pages.

### Files

Each file sent or received can contain multiple transactions. The [Files](https://portal.stedi.com/app/core/file-executions) page shows every file you have exchanged with trading partners, its processing status, and the number of transactions within the file.

You can filter files by various attributes, including status (such as `Failed` or `Completed`), direction, partnership, and fault (such as `failed to find guide`).

### Transactions

Individual [**Transactions**](https://portal.stedi.com/app/core/transactions) only appear after an entire file has been successfully processed. Every transaction that has been successfully sent to or received from your trading partners appears in this list.

You can filter transactions by various attributes, including transaction set, sender, receiver, direction, and usage (such as `production` or `test`). You can also search for specific transaction sets based on a business identifier, such as a purchase order number.

## Inspect raw data

You can review the raw EDI or JSON data for processed files and individual transactions. Click the name of the file or transaction to review its data.

### View a file execution

The file execution detail page contains processing results and the entire source of the original, unmodified file. You can copy or download the source file to your local machine.

### View a transaction

The transaction detail page includes two tabs that display different levels of information.

* **Details:** Displays metadata about the transaction, including the sender, receiver, the guide used for validation, and more.
* **Inspector:** Shows the transaction payload in a human-friendly view, which you can use to understand the contents of the transaction.

You can also view and download the raw EDI or JSON data for a transaction.

<Tip>
  **Advanced EDI users:** When viewing the raw EDI for a single transaction, the
  transaction EDI view includes the `ISA` (Interchange Control Header) and `GS`
  (Functional Group Header) from the source file. However, it does not include
  any other transaction sets that were in the source file, so the segment counts
  may not total correctly.
</Tip>

## Manage failed files

You can review the processing status for all incoming and outgoing files on the **Files** page.

You can individually retry or ignore failed files. You can also bulk retry or ignore multiple files at once.

* To bulk retry, click **Retry**. Core automatically retries processing for every file with the Failed status.
* To bulk ignore, click **Ignore**. You may want to ignore executions when they contain an outdated version of a file that you no longer need to retry.

Typically, you would retry a file execution if you have resolved the issue that caused the failure. For example, if a file failed because it was missing a required segment, you could retry the file execution after marking the segment as optional in the guide. You would ignore a file execution if you do not want to reprocess the file. For example, if you inputted the failed file to your system manually, you could ignore the file execution to prevent it from being processed again.

### Bulk processing

Before you initiate a bulk retry or ignore, you can filter the list of files to only show the files you want to take action on. For example, you could filter the list to show only files with a certain fault reason, and then bulk retry or ignore all of those files.

To bulk retry or ignore, click **Retry** or **Ignore**. After a confirmation step, Stedo triggers a retry or ignore for every file with the `Failed` status that matches your selected filters.

## Data retention

Artifacts refer to the transaction and file execution payloads from files Stedi has processed. They contain the actual input/output transaction data in EDI, JSON, or another format. Artifacts do not include the metadata about a transaction or file execution, such as whether it was processed successfully.

By default, Stedi retains your artifact files for 10 years. In some cases, you may want Stedi to remove artifacts to comply with PII/PHI retention policies. You can configure data retention on the [EDI Settings](https://portal.stedi.com/app/core/settings) page.