Troubleshooting
This document outlines the steps an Admin User should follow to triage and resolve background issues. Currently this feature is only supported for Jira and Alation integration issues.
{% hint style="warning" %} Only Admin users can access this feature {% endhint %}
Health Check (UI Method)
A quick way to check the current status of the integrations.
Navigate to Data Observability UI with Admin user, and specify your tenant.
On the top right menu, click the warnings icon.
This will list any open issues if existing
Deeper Diagnosis (API Method)
For issues that aren't immediately clear from the UI or for checking deeper job details, use the Data Observability API.
Query Parameters
Parameter | Type | Description | Required | Default |
|---|
limit | Integer | Maximum number of error records to return. Used for pagination and managing response size. | False | 100 |
Response
The response is a list of objects, each representing a single background error event:
JSON
[
{
"timestamp": "2025-10-28T14:01:00.000Z",
"error_class": "INTEGRATION_JIRA",
"message": "Some error...",
"exception_type": "RuntimeException",
"stack_trace": "additional multiline info...."
},
// ... more error objects
]
Field Definitions
| |
|---|
| Field | Description |
$\text{timestamp}$timestamp | The exact time the error occurred. |
error_class$\text{error\_class}$ | Categorization of the error source. Possible values:
INTEGRATION_JIRA: Error related to ticket creation/updates
INTEGRATION_ALATION: Error related to catalog synchronization. |
message$\text{message}$ | A concise, human-readable summary of the error. |
$\text{exception\_type}$exception_type | The underlying programmatic exception type. |
$\text{stack\_trace}$stack_trace | Detailed technical information, including the call sequence. |
📝 Example Usage
This example retrieves the 5 most recent errors from the prod_tenant.
Request
HTTP
GET /my-actian-backend/prod_tenant/errors?limit=5
Response (Abbreviated)
JSON
[
{
"timestamp": "2025-10-28T14:05:30.000Z",
"error_class": "INTEGRATION_ALATION",
"message": "Alation API returned 401: Invalid API token or insufficient permissions.",
"exception_type": "UnauthorizedException",
"stack_trace": "..."
},
{
"timestamp": "2025-10-28T14:01:00.000Z",
"error_class": "INTEGRATION_JIRA",
"message": "Failed to create issue: Field 'priority' is required.",
"exception_type": "JiraServiceException",
"stack_trace": "..."
}
]
Last modified date: 02/20/2026