# Automation reports - System errors

<figure><img src="/files/da6442ce1be3185174754e1c6db29e8300b7f71c" alt=""><figcaption></figcaption></figure>

#### Error Notification Example

As shown in the screenshot below, you can view a list of recent system errors:

<figure><img src="/files/c89a1394504e574cbc19b6ec085d29e099ca3a31" alt=""><figcaption></figcaption></figure>

Each notification provides important details:

* **Action/Condition/Trigger**: Indicates which element of the automation failed. In the example, the action is "Send Webhook."
* **Location**: Shows in which automation the error occurred. In the example, it is "SAC Automation."
* **Affected Lead**: Identifies the specific lead where the failure occurred. In the screenshot, the affected leads are 7321, 7375, and 3894.
* **Time**: Indicates when the failure was detected.

### Investigating and Fixing Failures

Once a failure is identified, it is crucial to investigate it to understand the root cause and implement the appropriate fix. Here are some recommended steps:

#### Step 1: Access the Notification

By clicking on the error notification, you will be taken directly to the specific lead. This feature allows you to quickly check what happened and facilitates diagnosing the problem.

#### Step 2: Check the Automation Configuration

Review the automation settings where the failure occurred. Verify that all triggers, conditions, and actions are configured correctly. Common errors may include:

* Triggers configured incorrectly.
* Conditions that do not match the expected criteria.
* Actions that were not properly programmed or authorized.

#### Step 3: Analyze the System Logs

Examine the system logs for more details about the failure. Logs can provide valuable information about the system state at the time of the failure and help identify underlying issues.

<figure><img src="/files/2745131a4acdfee136e1ec28b38fda60c95eb0e3" alt=""><figcaption></figcaption></figure>

#### Step 4: Test the Automation

After making the necessary corrections, test the automation to ensure the issue has been resolved. Use test data to simulate the conditions that caused the failure and confirm that the action executes correctly.

### Conclusion

Automation failures can be frustrating, but with the right tools and approaches, it is possible to identify and fix them efficiently. The Sprinthub platform offers an intuitive interface to manage and resolve these issues, ensuring your customer service system runs smoothly and effectively.


---

# 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.sprinthub.com/en/common-questions/automation-reports/automation-reports-system-errors.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.