# 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://content.gitbook.com/content/q2i9CKCFbySxr6jRoJfA/blobs/G4tVnUzydhfYTjyHVCNV/MicrosoftTeams-image%20(59).png" 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://content.gitbook.com/content/q2i9CKCFbySxr6jRoJfA/blobs/MRQYUjRD1SweKkN7lUqi/MicrosoftTeams-image%20(60).png" alt=""><figcaption></figcaption></figure>

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

## Component Failure & Navigation to Failure Analysis

The component failure is indicated by a red color flag in the Pipeline Workflow. The user gets redirected to the Failure Analysis page by clicking on the red flag.

* Navigate to any **Pipeline Editor** page.
* Create or access a Pipeline workflow and run it.
* If any component fails while running the Pipeline workflow, a red color flag pops-up on the top right side of the component.

<figure><img src="https://content.gitbook.com/content/q2i9CKCFbySxr6jRoJfA/blobs/3cism4nr0fHLzQcsK7mm/image.png" alt=""><figcaption></figcaption></figure>

* Click the red flag to open the Failure Analysis page.
* By clicking the ellipsis icon for the failed component from the **Failure Analysis** page, the user gets options to open **Monitoring** or **Data Metrics** page for the component.
* The cause of the failure also gets highlighted in the log.

<figure><img src="https://content.gitbook.com/content/q2i9CKCFbySxr6jRoJfA/blobs/dHnh07yoOJaPHJCiWjr5/image.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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.bdb.ai/data-pipeline-2/getting-started/pipeline-workflow-editor/pipeline-toolbar/failure-analysis.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.