> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/common-questions/automation-reports/automation-reports-system-errors.md). # Automation reports - System errors
#### Error Notification Example As shown in the screenshot below, it is possible to view a list of recent system errors:
Each notification provides important details: * **Action/Condition/Trigger**: Indicates which automation element failed. In the example, the action is "Send Webhook". * **Location**: Shows in which automation the error occurred. In the example, it is "Customer Service 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 solution. 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 makes diagnosing the problem easier. #### Step 2: Check the Automation Configuration Review the settings of the automation where the failure occurred. Check whether all triggers, conditions, and actions are configured correctly. Common errors may include: * Incorrectly configured triggers. * 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. The logs can provide valuable information about the system state at the time of the failure and help identify underlying issues.
#### Step 4: Test the Automation After making the necessary corrections, test the automation to ensure the problem has been resolved. Use test data to simulate the conditions that caused the failure and confirm that the action is executed correctly. ### Conclusion Failures in automation 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 for managing and resolving these issues, ensuring that your customer support system runs smoothly and effectively. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/common-questions/automation-reports/automation-reports-system-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.