> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zentien.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> View, filter, and investigate errors from your Salesforce orgs.

## Overview

The Errors page has two views, toggled at the top right: **Dashboard** and **List**.

## Dashboard view

The Dashboard view gives you an analytical overview of errors over the last 30 days:

* **By type** — a breakdown of error volume by event type (Apex exceptions, Flow faults, handled errors)
* **Users impacted** — how many distinct Salesforce users triggered errors
* **Error trend** — a 30-day bar chart showing daily error volume, so you can spot spikes and see when issues started or resolved

Use this view to understand patterns — which types of errors are most common, whether volume is increasing, and which days had the most activity.

## List view

The List view shows all individual errors captured from your connected orgs. Use the filters at the top to narrow down:

* **Date range** — filter by when the error occurred
* **Org** — filter by a specific connected org (shown when you have more than one)
* **Event type** — Apex exception, Flow fault, etc.
* **Severity** — Info, Warning, Error, Critical

Click any row to open the full error detail.

## Error detail

Click any error to open the detail view. You will see:

* **Error type and automation type** — e.g. `APEX_EXCEPTION`, `FLOW_FAULT`
* **Class/Flow name** — the source of the error
* **Error message** — the full exception message
* **Stack trace** — full context including org, user, batch job ID (for batch errors), and line numbers
* **Org** — which Salesforce org the error came from
* **Environment** — Production or Sandbox
* **Occurred at / Received at** — when the error happened and when Zentien received it

## Open in Salesforce

For Apex errors, the **Open in Salesforce** button takes you directly to the relevant record or debug context in your org.

For Flow errors, the **Debug in Flow Builder** button opens the exact Flow version that failed — ready to debug.

## Creating a Jira ticket

If your organisation has connected Jira, a **Create Jira Ticket** button appears on the error detail page. Click it to select a project and issue type — both are pulled live from your Jira account. Zentien populates the ticket with the error message, stack trace, occurrence details, and a link back to Zentien.

Once a ticket is created, a linked badge (e.g. `SCRUM-7`) replaces the button and links directly to the issue in Jira.

See [Jira integration](/integrations/jira) for setup instructions.

## AI analysis

Every error detail page has an **Analyze with AI** button. Click it to send the error context to Zentien's AI agent, which returns a structured diagnosis in seconds:

* **Recommended owner** — who should triage this: Salesforce Admin, Developer, Integration Engineer, etc.
* **Probable root cause** — a bulleted breakdown of what likely caused the error
* **Suggested fix** — step-by-step remediation, with code blocks where relevant
* **Confidence level** — High, Medium, or Low based on available context
* **Missing context** — what additional information would improve the diagnosis
* **References** — relevant Salesforce documentation and best practices

The result is stored and reloads automatically on subsequent visits — you do not need to re-analyze the same error.

AI analyses count against your plan's monthly credit limit. Your remaining credits are shown at the bottom of each result and on the Account page under **Plan & Usage**.

| Plan       | AI analyses/month |
| ---------- | ----------------- |
| Starter    | 10                |
| Team       | 50                |
| Enterprise | 500               |

## Error types

| Type             | Source                                                     |
| ---------------- | ---------------------------------------------------------- |
| `APEX_EXCEPTION` | Unhandled Apex exception (batch, scheduled, trigger, etc.) |
| `FLOW_FAULT`     | Flow fault path triggered                                  |
| `HANDLED`        | Explicitly logged via `ErrorLogger.log()`                  |