> For the complete documentation index, see [llms.txt](https://docs.bdb.ai/data-pipeline/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdb.ai/data-pipeline/~/changes/hPXwcPgG9oW1n2fHDeOk/getting-started/pipeline-workflow-editor/pipeline-toolbar/failure-analysis.md).

# Failure Analysis

Failure analysis is a central failure mechanism. Here, the user can identify the failure reason. Failures of any pipeline stored at a particular location(collection). From there you can query your failed data in the Failure Analysis UI. It displays the failed records along with cause, event time, and pipeline Id.

{% hint style="info" %}
*Check out the below given walk-through for failure analysis in the Pipeline Workflow editor canvas.*
{% endhint %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuq3RSHHup7fjHYaspk7y%2Fuploads%2F7hHdsRhzM41AzeYMtTqU%2Ffailure_analysis_video_AdobeExpress.mp4?alt=media&token=772d5abf-5630-4366-b00a-f070af8aece2>" %}

* Navigate to the ***Pipeline Editor*** page.
* Click the **Failure Analysis** icon.

<figure><img src="https://363587200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuq3RSHHup7fjHYaspk7y%2Fuploads%2FQmPKozcOEIBPWAoqwkeV%2FMicrosoftTeams-image%20(59).png?alt=media&amp;token=4cd02562-af60-4588-b1a5-7139992c3f0a" alt=""><figcaption></figcaption></figure>

* The ***Failure Analysis*** page opens.
* **Search Component:** A Search bar is provided to search all components associated with that pipeline. It helps to find a specific component by inserting the name in the Search Bar.
* **Component Panel:** It displays all the components associated with that pipeline.
* **Filter:** By default, the selected component instance Id will be displayed in the filter field. Records will be displayed based on the instanceid of the selected component. It filters the failure data based on the applied filter.

**Please Note the Filter Format of some of the field types.**

| **Field Value Type** | **Filter Format**            |
| -------------------- | ---------------------------- |
| String               | data.data\_desc:” "ignition" |
| Integer              | data.data\_id:35             |
| Float                | data.lng:95.83467601         |
| Boolean              | data.isActive:true           |

* **Project:** By default, the pipeline\_Id and \_id are selected from the records. If the user does not want to select and select any field then that field will be set with 0/1 (0 to exclude and 1 to include), displaying the selected column.

{% hint style="info" %}
*<mark style="color:green;">Please Note</mark><mark style="color:green;">**:**</mark> data.data\_id:0, data.data\_desc:1*
{% endhint %}

* **Sort**: By default, records are displayed in descending order based on the “\_id” field. Users can change ascending order by choosing Ascending option.
* **Limit:** By default, 10 records are displayed. Users can modify the records limit according to the requirement. The maximum limit is 1000.
* **Find:** It filters/sorts/limits the records and projects the fields by clicking on the find button.
* **Reset:** If the user clicks on the ***Reset*** button, then all the fields must be reset with a default value.

<figure><img src="https://363587200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fuq3RSHHup7fjHYaspk7y%2Fuploads%2FyA0l686o9f8NOOW9D8eE%2FMicrosoftTeams-image%20(60).png?alt=media&amp;token=bd084e91-25d9-4b95-81b3-1efa9a761cef" alt=""><figcaption></figcaption></figure>

**Cause:** The cause of the failure gets displayed by a click on any failed data.