> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/general-information/coda-portal/key-features/data-insights/3.-transaction-failures-dashboard-details-page.md).

# 3. Transaction Failures Dashboard Details Page

The Transaction failure dashboard gives an overview of payment success rates and error code analytics for your transactions.

You can easily identify the most frequent error codes that are encountered in a given period and dive deeper to analyze the reasons for the failed transactions.

We also provide Coda’s average payment success rate trendline as a benchmark for comparison.<br>

<figure><img src="https://files.readme.io/4e75272-image3.png" alt=""><figcaption></figcaption></figure>

You can also check the daily error code analysis using the below chart and identify the days with the highest failures for a deeper analysis.\
\
*For example here, Sep 24th Go-Pay experienced the highest number of failed transactions.*

<figure><img src="https://files.readme.io/676998c-image1.png" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coda.co/general-information/coda-portal/key-features/data-insights/3.-transaction-failures-dashboard-details-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.